Hi
Apologies for the longwinded explaination of my problem but I wanted to be thorough and to let you have as much info as poss to know what I have tried and I think I have it mostly down here..
I recently sucessfully (I think) rooted my i9100 with Neat Rom 4.4.2, which seems very nice
I also have two ZTE Kis phones (via Virgin) which I thought I would try to revive.
I managed to flash one with Firefox OS and it seems fine for the most part although it flickers occasionally
The other one that I had rooted ages ago I eventually managed to reset my recovery via a terminal emulator and flashed a Rom back to its original state except with an unbranded rom courtesy of http://blog.podtwo.com/android/rom/de-branded ROM for ZTE Roamer2 [gingerbread].html THANK YOU SEBASTIAN
As this was not ideal as the storage space quickly disappears I though I would try to flash it with something else... and after some looking around I went here http://www.youtube.com/watch?v=n_DJhaNH14o and downloaded the miscellaneous files attached (first dumb move)
I then tried to flash each of these Roms in no particular order and finally got one of the Xperia Roms to take me to the install stage (2nd dumb move) I was working on some other stuff and yessed away in my own smugness only to find that the rebooting phone showed a green android that gradually faded to a blueish whiteout...
It also would not boot to recovery! power + volume = same android fading away...
It also would not boot to FTM
My main OS - OSX could not recognise the phone via adb/fastboot etc so I decided to try Win 7 (3rd or possibly a lot more by now dumb move)
so I booted to windows and low and behold... adb/fastboot could not see the device upon opening my Browser to try to find a solution I discovered that my Browser had been taken over by Conduit... (I am certain it was not before attaching the Kis and the suspect rom) and I was bombarded by a number of options to remove malware threats and virus' etc.. figuring something was wrong (first smart move) I switched operating systems back to OSX and ran Clam scan and Sophos scan of Windows drive (infected with something in the region of 40 nasties) I quarantined and deleted all the nasty infected files. I booted into Linux and ran ClamTK scan of the windows drive which found something in the order of 1200 threats.. some of which were standard methods used by programs but I spotted a few trojans I think amongst the readout.
I have deleted the Rom files and formatted the SD card that it was on.
Neither ADB nor Fastboot sees the infected/soft bricked Kis device from any OS
I have discovered too that the infected Kis does actually do different things when volume buttons are held down in conjunction with the power button (I am guessing that although the rom was corrupt - or perhaps not meant for my device) the phone is still trying to enter FTM mode as it just boots to a red light on.
From Linux in terminal (lsusb, usb-devices and dmesg | tail) all identify the device - attached file which has a different device id depending on the "mode" it is in when I attach it - Vendor ID is always 19d2, but Device ID is either 1353 or 0112 (the latter is when it is in FTM? mode - Vol down, power on , red light constant)
OS X also see the device: when the device ID is 1353 it identifies it as ZTE HSUSB Device, serial no ROAMER2, version 2.29, ZTE Incorporated. Whne device ID is 0112 it identifies it as ZTE WCDMA Handset Diagnostic Port
Win 7 sees it in "FTM" mode as ZTE Handset Diagnostic Interface (DSU)
Now I have... (mainly from OSX and more recently unbuntu 12.04) with my limited intellect and even more limited knowledge of programming and restricted understanding of terminal commands tried to have tried to cp files directly to the device, I have looked to try to boot from an sd card, I have tried to go into the recovery mode even though I can't see the screen and navigate blindly to the update.zip or recovery.img etc --- I have put them all on the card. I tried to do this http://linux-sunxi.org/Boot_Android_from_SdCard - but got a failure around "awutils, make" I have looked at Odin, Heimdall options, I have tried to adapt other solutions for different phones to mine (which was how I somehow or other managed to recover my CWM through terminal emulator in the first place). I have tried through ZTE to get thir automatic update program/instructions.zip (which despite being on broadband was proposing to take something in the region of 2 to 3 hours to download 136MB....! made me think that that might be how long it might take to copy my 4 and a half ish Terabytes of data... (paranoid now? MAYBE) so I cancelled the download and rebooted to Linux where I feel comparatively safe!?
BUT NOW I AM STUCK
I have the Unbranded rom and CWM recovery I can see the device but I don't know how to force the two together... can anybody help me (I have just tried very hard to resist an Obi-Wan-Kenobi joke)
I hope someone can help
[Q] Xolo a500 stuck on Boot Logo&Sim card is missing or error & QCN restore failed&
Hi,
I have Xolo A500 Device which is rooted, and i have installed Xperia moded custom rom then i have some issues in performance, so i have tried to increase ram by using swapper 2 but i am not aware of the harmness of swapper 2.
And i have installed swapper 2 before configuring disk's then i used that application and configured the application for ram increase without configuring the disk, then i restarted my mobile it won't boot anymore it just given the vibration.
then i tried lot of methods but i cannot able to do anything, while trying to fix i used google mini partition tool and tha android system's partitions has been detected in that /system,/misc,/data, /cache,/swapper, /ram like drivers i found so i deleted /swapper and one more drive i deleted(i do not know which drive i deleted) i thought like windows partition we can form new partition with bigger memory like that to increase the ram memory.
And i given mobile for service, the service man used usb jig method to enter into download mode then installed the original os but the both sim has not been detected.
Here my main problem starts
and i have use so much of techniques to fix sim detecting issue no improvement
again installed custom rom and then yesterday i tried installing "https://drive.google.com/uc?id=0B6xlBPoXgsR3R253RkdWNHgzdEE" official 4.1.1 601mb rom from windows while flashing rom it given the alert message "QCN Restore Failed" now the mobile stuck at boot logo does not detect in any of the system help me out from bothh of the issue.
Thanks in advance..
Note : i am thinking that /misc which i wrongly deleted directory is missing , so while installing rom it skipped that directory and then for installing original rom "Restore QCN Failed" - There is a connection between everthing
the error messages which i am getting is "sim card is missing or error"
"unstructured rom"
"QCN Restore Failed"
while taking nandroid backup modem.img and some files zero byteshttp://forum.xda-developers.com/general/xda-assist/xolo-a500-imei-serial-unknown-unbricking-t2988393
Please Help me out..
Thanks in Advance..
Hi there,
Please read and ask in one of this threads:
[INDEX] ALL ABOUT XOLO A500s PHONE
or
[Guide] Xolo A500S : ROOTING, ROMES ,CWM & STOCK RECOVERY,SAFE & FACTORY MODE
Good luck
Hello,
First time writing on the forum so please tell me if I do something wrong .So ,yesterday i've installed kubuntu on my nexus 7 , via platform tools (flashing img on fastboot).In kubuntu i have installed gpartition with terminal ,because i've saw that i only have 6 gig of free memory on 16 gig nexus 7 , and i wanted to know why.I opened it and when he finish analyze my tablet ,he find 15 gig of unalocatted space.So i decided to format that partition.After a minute he promted an error ,that he can't create disk label and adviced me to reboot before making any changes.After i closed all apps ,i rebooted my tablet , but something happened, she doesn't boot up any more.I tries diferent buttons combo,but she doesn't boot up,and i noticed that i can't access bootloader or custom recovery or fastboot.From some resources on internet i've found that it may be hard bricked.Can anyone tell me if is it hard bricked( i hope not) and if is it , how to solve that? I also want to add that i don't know to use nvflash , and i've never maked blob file backup. Can anyone pls help me?
I have a Xperia L with CM 12 installed successfully.Recently i was poking around with it's partition table using ADB to increase my internal storage and might have done something wrong.Now the phone doesn't start,doesn't go in CWM,doesn't go in fastboot and doesn't connect as an ADB device as well.The phone is detected as a HID complaint device(Don't know what that means) and i have hit a wall repairing this.Any help would be appreciated.Is there some special application for this?Or something else?Do i need to interact directly with Motheroard by opening the phone!There's got to be some way right?
Not losing hopes on this one.
Please help
I currently have 2 external hd I use for OTG, 3tb Passport Ultra and a 4tb Passport, both formatted to exFat. At first, the 4tb works like a charm. Suddenly, got an error from it from my android tablet that it was damaged and needs to be reformatted. Plugged it into my computer and my computer recognized it and its contents so i rand chkdsk and found no errors. When I tried it again on my tablet, it displayed the same error so I opted to format it again to exFat and copy some videos on it and tested it on my tablet. Unfortunately I ran into the same error. Basically my tablet cant recognize this external HD anymore without help of stickmount on exfat or paragon on ntfs. My other hd still works even though I reformatted it again and my tablet seems to recognize it without a problem. Has anyone come across something like this before?
Hi !
Please give us more info about your tablet , model / android version/ software status ( rooted , unblocked bootloader , mods installed ) in order to provide assistance , thank you
Cheers !
xanthrax said:
Hi !
Please give us more info about your tablet , model / android version/ software status ( rooted , unblocked bootloader , mods installed ) in order to provide assistance , thank you
Cheers !
Click to expand...
Click to collapse
My tablet is a Galaxy Tab S2 (T-810) 5.1.1. stock root.
I feel that the problem lies with the external hd instead. All my android device sees it as corrupted but it works with no problem with Windows. I can only mount it with stickmount and paragon.
I don`t know how it worked at first , 4TB hdd needs lot of power to work on a Samsung device , you may need a Y cable
If stickmount does the trick then keep on using it , it may be software related , maybe an updated application did something
I may suggest to reflash the stock firmware and try on a clean system but a 4TB hdd it looks too much for a tablet
xanthrax said:
I don`t know how it worked at first , 4TB hdd needs lot of power to work on a Samsung device , you may need a Y cable
If stickmount does the trick then keep on using it , it may be software related , maybe an updated application did something
I may suggest to reflash the stock firmware and try on a clean system but a 4TB hdd it looks too much for a tablet
Click to expand...
Click to collapse
I use a y cable on it. The thing is, it used to worked before. One day it suddenly said that I need to reformat it again. I have another external hd (3tb) and it works no problem. I think something happened on the hard drive itself.
It could be a connector problem as well, a shortcut or something
xanthrax said:
It could be a connector problem as well, a shortcut or something
Click to expand...
Click to collapse
On unrelated note, sorta forgot how to do the whole reflash+root etc so could you point me to the right direction and should i stick to 5.1.1 or go 6+?
Gregole84 said:
On unrelated note, sorta forgot how to do the whole reflash+root etc so could you point me to the right direction and should i stick to 5.1.1 or go 6+?
Click to expand...
Click to collapse
A good index is here , I would suggest the latest firmware
https://forum.xda-developers.com/tab-s2/general/index-samsung-tab-s2-one-index-t3544310
Good luck !
I was wondering, could i boot to twrp recovery and install a rooted stock 6.0.1. Rom?
I guess yes , the version is correct so it is for your device
Good luck !