Related
Hello all,
may i´m not right in this forum, but i can´t see a matching one.
I bought a used android phone from someone who was somekind of "not friendly".
Coming from winmob, i´m an android noob.
After reading here and at the net about the possibilities of android apps, i am now a little afraid to go online with the device with my sim inside, because i am not sure if the seller may installed some spy-apps and then may get my personal data, my location, or may remotely crash the device after a while.
I´ve already set it back to factory. But as i read, there may some apps which will survive this. I´ve also already rooted and installed some "su-apps" to look inside processes and files.
But there are many apps and services i cannot judge if they are standard from the OS and safe, or not.
Are there tools to investigate if something "weird" is installed, or may blacklists of spy-apps?
Thx in advance.
flash back to a stock rom, then youll know you are safe.
Sent from my PC36100 using XDA App
thanks for the quick reply
you mean, when i run
settings - security - back to factory (my translation from german)
is enough and no "backround-spy-process" is able to survive within this process?
thx
Search the market for Dr.Web perhaps?
syrenz said:
Search the market for Dr.Web perhaps?
Click to expand...
Click to collapse
will have a look about it, thx
Simply doing the factory reset may not get it.
If you're rooted, install a custom recovery and then install a custom ROM (could be custom, or just a rooted stock rom). You'll wipe the various partitions when you install the rom, and that should clear anything up.
We aren't going to be able to help much more than that without knowing at least what phone you have. Note that there are phone-specific subforums here, I would recommend that you find the one for the phone you bought and ask in there.
the orange bandit said:
Simply doing the factory reset may not get it.
If you're rooted, install a custom recovery and then install a custom ROM (could be custom, or just a rooted stock rom). You'll wipe the various partitions when you install the rom, and that should clear anything up.
We aren't going to be able to help much more than that without knowing at least what phone you have. Note that there are phone-specific subforums here, I would recommend that you find the one for the phone you bought and ask in there.
Click to expand...
Click to collapse
thx for your suggestions....
as i said, i´m an android noob and a little afraid to install a custom ROM and if it will crash then.
it was on 1.6 and i already updated it to 2.2 (OTA) ... did that may did the same as to install a new (custom-) ROM?
btw. it´s a streak and i spent a lot of time to setup apps, widgets, etc.
are there really no tools to detect known spy-apps?
thanks to all
Dr.Web doesn't do that? I got the impression that was what it was for... :shrug:
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Stephen Wayne Hamilton said:
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Click to expand...
Click to collapse
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
drago10029 said:
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
Click to expand...
Click to collapse
If needed, I could back up my /system folder and send it to you.
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
it's alright man. someone on android forums has already made a custom ROM. so the ball is rolling on out weak old device :laugh:
build.prop?
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
did you ever get around to doing this? there is supposedly a stock image on androidforums but when I opened the Zip, all it had was the stock apps, no build.prop, which I think I blew away with xblast (xposed plugin). now I hang on the boot screen image. there is a stock Rom for the z993 our there, which I suppose I could use, because they are supposed to be the same phone, just different carriers... but then I need to get the at&t apn's and it is just a PITA. so if you could post /system backup or just a stock build.prop, that would be great!
(I'd post links to these rooms but I guess I'm too new of a member... I can provide them if needed.)
I'm way late on this, but just thought I'd post to say that I no longer have the device, and I was never able to fix it.In any case, I hope the rest of you guys get it fixed. It seemed to be a halfway decent phone, although a bit sluggish at times. But beyond that, with all the bloat removed, I'd say it ran pretty well for the duration of time that I had it (less than a month). I currently have a GNote 3 (T-Mobile) and a GNote Pro 12.2" now and it's just awesome, I'm really loving them.
Sorry, accidental double-post (can't figure out how to delete this post, the "Edit/Delete" button doesnt appear to have any option to entirely delete a post).
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
alirezayami said:
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
Click to expand...
Click to collapse
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
alirezayami said:
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
Click to expand...
Click to collapse
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
AlexZap said:
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thnx Alex
I would highly appreciate if anyone tell me what ADB Driver I should use for ZTE Z992. I almost understood all the procedure in the links but now the problem is despite I tried different ADB Drivers, but still ADB reboot-bootloader boots phone again in Normal bootloader.
Also Fastboot devices command does not see the phone, while ADB Devices command see it.
Seems bootloader is locked. Right? What should I do?
This is the method I used when I rooted my avail2 :
http://androidforums.com/zte-avail-2-zte-prelude/821217-how-root-zte-avail-2-z992-guide.html
The author (and I) just used the included drivers from zte that come with the phone. From what I remember, fastboot worked fine. Just hold the volume down button then turn the phone on. It will seem to lock on the start screen, but this is the bootloader. Then connect your cable and try your fastboot commands.
If you are already rooted, you can just download the package here
http://androidforums.com/prelude-all-things-root/797487-cwm-recovery-installer-zte-prelude.html
And skip the middle section, using the impactor to root (13 and 14).
Depending on what's wrong with your phone, you could also try just using the stock recovery and doing a system reset there. It will wipe any bad custom settings, but if the rom is still viable it might get you up and running again. It got me out of a bootloop without re-romming the whole thing. And with titanium backup or system app mover you can reinstall anything you need in the system partition.
*edit - Damn kindle auto correct
Sent from my KFTHWI using Tapatalk
A bit to much fiddling resulted in disaster
Hello XDA forum users,
I'm about ready to toss this phone in the trash. I have an AT&T Avail 2 with model number z992, which is apparently manufactured by a company called ZTE. First I think it would be helpful to explain what I've done to the phone and perhaps others out there can tell me if I've destroyed the phone or if it can be fixed.
A friend of mine sold me the phone for 10 bucks, its in great condition which is why its such a shame that it seems perma-bricked. I have no need for the phone aspect of the device, I simply wanted to "convert" it to a handheld media/application player, like an ipod or tablet for example. The phone comes with several bundled software applications that I find completely useless and wanted them removed, EX. AT&T Navigator and other AT&T software, plus a bunch of google applications.
The first thing I did when I decided to try and customize it was to use Kango's root tool which worked and rooted the phone. I was all excited that it worked and continued by installing the Super User application which allowed me to gain full control over the device. (I should have stopped there.) After the successful phone root I then installed a 3rd party app called NoBloat and used its uninstall options to remove a lot of stuff. I couldn't tell you exactly what all was removed but looking back, it must have been more important than I realized at the time. I know I took out all the AT&T software, then all the Google stuff to, which destroyed the play store. I didn't take out anything that seemed like a system file but apparently the Google stuff is the system files. The phone still worked in this state but it was erratic and things like Contacts would crash even if it was not running. So I considered that a failed attempt and commenced to do a factory reset using the recovery menu (Vol Up + Menu Key + Power button) but the factory reset didn't work, well not like it was supposed to. I had used the restore option before and it made the phone work like it was brand new. Now when the phone is powered on it will boot to the initial setup and ask me to choose a language, then it will get as far as the wireless connection screen (sometime not even that far) and the phone reports that "Unfortunately, Setup Wizard has stopped." and then I tap OK and the setup wizard restarts at the language screen. This is the state it is in now and I do not know how to fix it, I'm beginning to think there currently is no method to fix this.
Things I've tried so far include installing minimal ADB-Fastboot to try and sideload various ROM images, the ones I found here and other places. The phone is not recognized by Windows 7 though and the ADB does not work like it did on a motorola phone I did this to before. I've also purchased an inexpensive 8GB microSD chip with an adapter so I could put the ROM info on that and tried the "Update from external storage option" and that seems like it would work but none of the ROM's I've used will install. I guess because there is some kind of security feature built into the phones hardware which checks the data files for specific tags/sizes and therefore won't accept any of the ROMS I've tried.
There is no means to access the old file system anymore like most guides show, I do not have any CWM's installed nor any backup data whatsoever. It's been reset and now it seems the data it used to restore itself is, while not completely missing, damaged and will not reload anymore. All the guides I've read or watched usually show the user in the operating system or using software on a PC to type out commands. None of that works on this phone though, the phone as I just described it is basically bricked. Is there anything that can fix this, or is the phone a paper weight now? A functional ROM image from AT&T seems unlikely as they have absolutely no relevant information about this on the commercial website and the help and support seems like it's setup for old people who don't understand technology at all. If anyone out there has experience with issues like this then by all means let me know. If more information is necessary then I will be glad to provide it if available.
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Britton Burton said:
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Click to expand...
Click to collapse
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commands
adb.exe push cwm-z993.img /cache
adb.exe shell "su -c 'dd if=/cache/cwm-z993.img of=/dev/block/mmcblk0p17'
This should flash cwm if your phone is rooted and adb shell is working.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commandsp
Click to expand...
Click to collapse
I have not come across that particular file yet, I did try to google it and the only results it had were two and one of those was this post. Would you mind telling me where I might find a copy of the kaw202_recoverflasher.zip?
I managed to find the zip you were talking about and have downloaded it, for anyone else looking for it. I am unable to post links but I would have linked to the files you mentioned. For others looking for the same zip file search for "CWM Recovery Installer ZTE PRELUDE". That's the title of the thread I found the file on that Alex mentioned above. The instructions on the page don't seem like they apply to the situation I'm stuck in but I'll give it a whirl anyway and see if the files work.
If this forum is like the others I've read through so far then there is no real answer to the issue. The phone seems kind of new and not many of the power users on these forums use rinky dink phones like this one. You guys all have the 600 dollar models I guess. What bugs me about this this phone and the state I managed to put it in, is that the damn thing was programmed the first time when it was made. So it seems to me like there should be a way to reprogram the phone the same way the factory did it. Think about it, when they make the phones they don't have any information on the phone at all. It's completely empty, so there must be a way to load the software for the phone even if the phone has no data at all in the main storage. If the files in the recovery flasher.zip file work then I'll post back the results but if it's like the other files I've messed around with (which didn't do anything) then I'm throwing it in the trash can.
Anyway thanks for your response and for pointing me in a different direction Alex
---------- Post added at 09:15 PM ---------- Previous post was at 08:39 PM ----------
HELL YEAH!!! It worked thank you Alex,
I would have never figured this out without your help! The phone now has a version of CWM on it and the recovery menu is different. I just tried to install a ROM and it said successful. After the phone rebooted went back to the setup screen from ZTE but it still did the same thing. However this is progress and I should be able to "wander in the dark" and figure out a way to use the CWM to install a completely new rom. Any recommendations on a ROM to use for the z992?
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Britton Burton said:
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Click to expand...
Click to collapse
ze
Glad I could help, but none of the work was done by me, the guys over at android central did all the heavy lifting, I just pointed you in the right direction. I have a stock system e m image around here somewhere if you need it, tho installation will be a bit more complicated. If azazels rom ever gives you issues, ill dig it up and try and help you install it.
Sent from my KFTHWI using XDA Premium 4 mobile app
Hi all
Recently I upgraded from Samsungs stock 4.1.2 firmware to CyanogenMod 10.2 Stable (based on 4.3.1) using their installer program. Since upgrading the Wifi has been unusable and I have not managed to get the problem resolved through their forums so I have decided to go back to the stock rom.
Now that Samsung have re-released 4.3 for the S3 in the UK (after the one from last month which was pulled for problems) I would like to use this one as it fixes a bluetooth streaming issue I have endured for a long time. I can't find this new firmware for download anywhere so wondered if it is feasible to download say the stock rom 4.1.2 and then upgrade somehow? I have a red line on the bootup screen which shows it has been modified (which triangle away won't remove due to custom rom/bootloader or something like that) so I believe this means I will be blocked from then upgrading from 4.3 OTA but able to do so with Kies?
Being a novice at this I am obviously worried about breaking my phone and I am not sure if having i9300XXEMG4 as a baseband version is an issue among other things after reading the forums. As much as I have read about EFS and the downgrading modem problems, none of it is making sense to me at the moment, even after reading all the documents. Brain freeze maybe!
The cyanogenMod also changed recovery and unlocked the bootloader going by what I have read, is this an issue I need to worry about?
Any advice that can take away some worries and get me on the right path would be muchly appreciated!
You are posting in the wrong forum .
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
JJEgan said:
You are posting in the wrong forum .
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
Click to expand...
Click to collapse
Thank you for your post. I did follow a link in the !!ALL QUESTIONS GO IN THE Q&A FORUM!! OR THEY MAY BE DELETED!! sticky thread which took me to the Q&A forum where I thought I was posting. It is possible a confusion happened during the sign up process.
After reading those threads, two of which I had already read before posting, I have more understanding than I did before. Somehow I missed about the S3 not having a locked bootlader to begin with. I have backup up the EFS using Ktool but also understand it would have been more useful to do before flashing CM 10.2 as I now only have a EFS v2 backup rather than a version 1. What I am unsure of is what is my best action to take at the moment, going by the information I have. I can it is best not to go downgrade to earlier firmwares unless I wanted an added headache of the modem workarounds but do not see the best way to get back to a stock 4.3 firmware still.
I am on Three mobile (H3G) in the UK but don't think my phone is actually locked to them and don't know if that means the BTU is the option I should be choosing. Even so, when I check the firmwares on http://www.sammobile.com/firmwares/2/ I can only see a firmware added last month which I have to assume is the bad 4.3 update that hit the UK and was pulled after the problems it caused. If it was my best option for flashing, even with the problems it caused, how would I then go about getting the extra update that Samsung pushed out to fix the problem?
I saw the Korean factory flash in one of the threads too, not sure if this is too extreme (and potentially more dangerous) than the other options which may be available to me.
Obviously I would like to do this right the first time, rather than stumble backwards fixing all the mistakes I make at the time. So sorry if I am asking what may be simple to some. My knowledge of phones sucks and I wish I hadn't been tempted by the easy looking Cyanogenmod installer now!
Noticed after a few cache and devlik cleans and reboots that the wifi started working on the CM 10.2 mod but only for the main browser and hit and miss with google play. Every over app didn't work on wifi though, but did on cell. I googled all over to see many with similar problems, which suggested manually setting the time and date and static ip settings, clean davlik and updating play apps after deleting their cache.
None of them worked. So to potentially getting away from flashing, does anyone know any other ideas to resolve this? Wifi connects, stock google browser works, Play works flakey. Other installed browsers wont load any pages or connect to the net, such as speed testing app. The only unusual app that also works in a twitter app. Installed an app to see if there was a hidden proxy setting, but it found nothing, Really strange. All the apps work on cell.
Follow the guide in general forum, stickies, to flash back to stock BTU. Network lock is irrelevant to rom.
Choose either 4.1.2 or 4.3 but your baseband must be EMG or later as you now have efs v2.
Don't flash things you don't fully understand, any non Samsung rom has drawbacks you'll have to live with.
In the stickies is a world of information supposed to help you.
boomboomer said:
Follow the guide in general forum, stickies, to flash back to stock BTU. Network lock is irrelevant to rom.
Choose either 4.1.2 or 4.3 but your baseband must be EMG or later as you now have efs v2.
Don't flash things you don't fully understand, any non Samsung rom has drawbacks you'll have to live with.
In the stickies is a world of information supposed to help you.
Click to expand...
Click to collapse
Appreciate you giving me a direction to go. It seems the problem I had finding firmwares the last few days were due to Hotfile going offline and Sammobile rebuilding their index of firmwares. I found through the forums 4.3 BTU I9300XXUGMJ9_I9300OXAGMJ9_BTU.zip which contained a 1.5GB file called I9300XXUGMJ9_I9300OXAGMJ9_I9300XXUGMJ9_HOME.tar.md5 which I think is the correct one which I will try and flash later using the guides. It's not the new fixed 4.3, it's the older broken one but I guess in time I can apply the fix that Samsung are pushing out. This was part of my original question and now i have seen from other posts in the last few days that there is no full copy of the 4.3 anywhere.
The timing of me doing this appears to have been bad for a few of the above reasons, making working it out more difficult to work out for someone who has not done this before.
I can see from your signature and also your post that you think questions such as mine are easily answered in the various threads and through search. Personally I did try all those options first but either my lack of understanding or the overwhelming amount of information meant I was unsure as to what I should actually be doing, let alone which guide to follow. Even googling for BTU or searching xda to try and find what it means was fruitless so trying to put the pieces together is not easy if you have no experience with phones. I have programmed a Pi to do many tasks, built mainframe>SAS gateways and various technical challenges but I still struggle with all the phone flashing info
Many thanks again. Even a few words have been helpful
If you flash the kernel from the Chinese ZCUBMK it will fix all the broken parts of the current uk rom, until the latest ota emerges on xda.
I don't mind helping people who have made a genuine attempt to help themselves, my signature is aimed at the those who flash anything they find then demand someone give them an instant fix.
Your only mistake seems to have been the depth of research before you started, which could have been fatal to your phone -many first time flashes end up with a new motherboard required.
Sent from my GT-I9300 using Tapatalk
If the ota doesn't work in the next few day's I will try that kernel, thanks for that info!
I managed to flash the older official 4.3 firmware just now, so progress has been made A quick check shows me that the power on/lock screen lag problem is present so I assume the other issues will be there too. The red line showing the flash counter has gone and I got no modified phone error when attempting an ota update, as well as device status saying official, so I assume I should be able to upgrade that way when they allow more upgrades on the rollout server.
In case anyone else needs to do the same, this is what I did:
1) Downloaded https://mega.co.nz/#!DVxVgZZb!LIxKGA2Q_KbBH9APo_slOCdZNGJgfn1O6fxOF4C OkHA which I found via a thread titled [Official Firmwares] I9300XXUGMJ9 (Android 4.3) - Ireland (VDI) [04-11-13]
2) Followed the flashing instructions on this page
3) After flashing I got stuck at the Samsung boot screen with the blue light on, even after reseting a few times. So I powered off, held down the home button, volume up and then the power button which took me to the recovery screen where I chose the factory default option. All worked fine after that.
Thanks once again for your help with this boomboomer. A bit of direction was enough to give me the confidence to try it. It's nice to be back to a familiar interface (although it has changed from the 4.1.2 I had before) but the initial setup reminded me of all the bloatware installed. It's a fair bit slower than CyanogenMod was but it all seems to work ok. Once I get the ota update i'll root and freeze some apps to sort that out. Now to install TSF shell
I took a gamble buying a Chinese phone redmi-note 2 but sadly! it hasn't worked out for me.
All I wanted from it, was for it to do what it is supposed to do.
Bluetooth
Bluetooth doesn't connect to any of my devices, car, Hi-fi and not even my nexus 7!
Miui updater
Totally useless on my phone. This app crashes every time I select "choose update package"
I have looked for help on YouTube but the majority of videos seem to be Indian, using Indian versions of software where the updater app seems to work perfectly.
I managed to root my nexus 7 with ease but the redmi-note 2 is a nightmare.
I could really do with some of you android guru's to point me in the right direction! in finding a good beginners guide to finding all the apps and suitable rom for my phone, Or better still.! A way to get Bluetooth to work.
First of all check if your device has official rom or custom (if you bought it from China it probably has custom rom so flash official one).
Mine is working very good...
I second what ibeqa said - you're probably running a crapware-loaded ROM. Crashing updater is a good hint. You could also look into "about phone" section for the MIUI version, if it's something like 9.99.99 then it's crapware. "Legit" ROMs have version 7.xx.yy or 6.xx.yy. The crapware ROMs are IMHO the main reason why Xiaomi decided to lock the bootloader on RN3 and other newer phones. Because obviously, those ROMs give them bad reputation even though it's not their fault.
Bluetooth works fine for me, but sometimes it hangs up forcing me to restart it - not optimal but doesn't happen too often.
As for rooting, rooting the Nexus 7 (2012) was the same as RN2 for me - connect to PC in fastboot mode, flash recovery.img, reboot to recovery and flash a custom ROM. There are enough guides out there. For the RN2, fastboot can be accessed by starting the phone with the volume down key pressed.
Agree with the above. Please re-flash using official ROM via fastboot method and then try again. See http://en.miui.com/a-234.html
Android version 5.02 LRX22G
MIUI Version 66.77.33.00(LHMCNCH) Stable
Cpu octo core 2.2Ghz
Ram 2GB
I Have downloaded Update supersu 2.4 and miui HMNote2Global v7.2.2.0LHMMIDA_DA_d71ff21b81_5.0.zip are these correct please?
I installed CWM but have read that TWRP is the one I should be using! is that correct?
The trouble with the redmi 2 ,is there is too much conflicting information out there, making it very difficult for a newbie.
Is there any other things that I need to download?
This whole thing has really put me off the Xiaomi brand. I just expected bluetooth to work ! it is supposed to be standardised worldwide.
To you Guys it is probably fun to mess about with different roms, all I wanted was a working phone.
"MIUI Version 66.77.33.00" <- that's your problem right there. You reseller installed a crapware loaded ROM and has modified the version so that you never get an update (= he can spy on you forever), had you bought from another one, you would have gotten a working phone. I know mine did.
Putting blame on Xiaomi for this is misplaced, unless you want to blame them for being dev-friendly and leaving the bootloader unlocked. They reconsidered by now, though, their newer phones are locked.
In any case, yes TWRP is the way to go personally. CWM has cut important features like backup/restore (at least the version shipped with cyanogen roms I tried), so it's basically useless.
For the ROM, if you have downloaded it from the xiaomi page, then yes. You could also get the rom from xiaomi.eu if you want to use an European language.
If you just want official MIUI then you don't need to install custom recovery (use fastboot method instead as per official instructions). In fact the custom recovery will get removed next time you receive an OTA update.
Personally I use TWRP from this link http://en.miui.com/thread-224679-1-1.html because I wanted to install root. But only do this AFTER you install a clean ROM at the first place.
Crim Soukyuu said:
"MIUI Version 66.77.33.00" <- that's your problem right there. You reseller installed a crapware loaded ROM and has modified the version so that you never get an update (= he can spy on you forever), had you bought from another one, you would have gotten a working phone. I know mine did.
Putting blame on Xiaomi for this is misplaced, unless you want to blame them for being dev-friendly and leaving the bootloader unlocked. They reconsidered by now, though, their newer phones are locked.
In any case, yes TWRP is the way to go personally. CWM has cut important features like backup/restore (at least the version shipped with cyanogen roms I tried), so it's basically useless.
For the ROM, if you have downloaded it from the xiaomi page, then yes. You could also get the rom from xiaomi.eu if you want to use an European language.
Click to expand...
Click to collapse
I bought the phone from Gearbest.EU and expected it to be direct from Xiaomi, as I have never had a problem with this company before.
I have had another go at installing a new rom with the Mi suite and also with the miui flash tool and am not getting anywhere with it. I can't even root the damned thing as it boots into Mi when pressing vol up and start. This happened with CWM and TWRP.
I have said before,that I have little experience with android and perhaps I am going wrong somewhere! or the tutorial posters are using phones that have totally different roms to mine. ,It is very difficult when you have Indian,Chinese and global versions with many variations of each, the same seems to apply to CWM and TWRP.
Is there a way to install this via windows, ie formatting the phone and running an installer direct from pc?
I had a dabble with Linux mint and Artist in the past and found them quite user friendly, I can't believe that android is Linux based! I could have done a fresh install of windows, several times by now,the amount of time I have spent on this. Of course windows truly is global with only a couple of variations . Format disk, run and your away. Then hours installing software.
I am fast getting to the stage where I shall give it a bounce test, from a great height. :crying:
I am trying to get back to stock firmware/rom after having LineageOS.
I got Odin and downloaded several stock rom files and none of the work properly, I can flash them and the tablet starts in what looks to be the default initial setup but the apps keep stopping before I an even tap anything, sever apps like keyboard, one drive and so on, basically all apps crash at the same time.
I believe I am not getting the right rom, but I have no idea how to find out what the right one is, does the country really matter that much ?
Nrby said:
I am trying to get back to stock firmware/rom after having LineageOS.
I got Odin and downloaded several stock rom files and none of the work properly, I can flash them and the tablet starts in what looks to be the default initial setup but the apps keep stopping before I an even tap anything, sever apps like keyboard, one drive and so on, basically all apps crash at the same time.
I believe I am not getting the right rom, but I have no idea how to find out what the right one is, does the country really matter that much ?
Click to expand...
Click to collapse
Where did you get them from?
I used SamFirm_Reborn and got the correct multiple part 9er as I've flashed back to stock twice already.
Although my T825 is on LOS19.1 atm.
Were you using single or multiple part ROM?
bmwdroid said:
Where did you get them from?
I used SamFirm_Reborn and got the correct multiple part 9er as I've flashed back to stock twice already.
Although my T825 is on LOS19.1 atm.
Were you using single or multiple part ROM?
Click to expand...
Click to collapse
i downloaded from several sites, always the 4 part, always android 9 latest patch, tried the romanian version since I it was bought new in romania but that's probably not a guarantee
@Nrby I recommend using Samfirm as it downloads directly from Samsungs servers.
Just to make sure you get an original.
@Nrby btw which Odin version?
finished downloading/decrypting with SamFirm_Reborn_0.3.6.3, used Odin3_v3.14.4 to flash the files, worked well and I get the same issue after the reboot, it tries to initialize and then just keeps trying to close apps until it reboots, could this have something to do with the wrong rom ? how can I even determine what region I need at this stage ?
@Nrby which region code did you use?
checked here?
Samsung CSC Codes List (All) | Change CSC on Samsung Devices
Today, we'll explain Samsung CSC codes. Besides, we also have a list of CSC codes or region codes with a method to change CSC on Samsung.
www.droidviews.com
Was it at that stage connected to Wifi or mobile already?
bmwdroid said:
@Nrby which region code did you use?
checked here?
Samsung CSC Codes List (All) | Change CSC on Samsung Devices
Today, we'll explain Samsung CSC codes. Besides, we also have a list of CSC codes or region codes with a method to change CSC on Samsung.
www.droidviews.com
Was it at that stage connected to Wifi or mobile already?
Click to expand...
Click to collapse
never got there, the Samsung Keyboard is also one of the apps that keep crashing so I can't enter the password.
I'm not even sure if it has anything to do with the CSC, I can see the build in the recovery menue, the questions is am I seeing the original firmware code or the one I flashed now ?
Nrby said:
.... , the questions is am I seeing the original firmware code or the one I flashed now ?
Click to expand...
Click to collapse
Afaik you only see what you flashed.
Original ROM might be noted on the box it came with.
I'm no step further, I have no idea what the original rom was, and not sure how to find out
I don't even know if that might solve the problem
I've attached all the information I can gather from the box/tablet in it's current state
@Nrby I've compared on sammobile some stock ROM versions for Europe and for T825XXU3CTD1 and the CSC is at least identical between Romania, Greece, Czech, Germany, Poland. They all have the OXX.
I doubt that your problem has anything to do with the CSC as apps crash even before connecting to any mobile provider.
Tried flashing stock ROM several times one after another while staying in download/Odin mode all the time?
I remember that this helped me once on a different device.
thanks a lot, worked after around 4-5 flashes, it's a bit slow, might still have some issues but seems to run stable for now, really didn't expect this to work
Nrby said:
thanks a lot, worked after around 4-5 flashes, it's a bit slow, might still have some issues but seems to run stable for now, really didn't expect this to work
Click to expand...
Click to collapse
Glad that my hint helped.
Perhaps useful for other users if you mark the thread as solved then they find the solution when having the same issue.