This is the first time I've messed with this phone I've flashed many different models in the passed but this is the only one that is giving me issues and the worst part is that its not mine so any hell i will greatly appreciate it.
Here is what i did read what ever i can to get more accustomed to this phone. and searched everywhere to help me figure out what i can do.
So i flashed the unlocker. Coke 2.31
after i did that i flashed nfsfan's 1.5 rom using usb cable.
no i cant get into the operating system at all it hangs at the vzw splash screen.
Is there a way to get this phone back to normal? i cannot connect thru activesync and when i tried to reflash using sd card it shows the loading screen for a split secon then goes back to the bootloader.
Please help its my bros phone i need it up and running asap.
Thank you
This post helped quite a bit
ArcaneMagus said:
Just thought that I would post what happened to my phone and the steps that eventually recovered it in case it helps somebody else:
My phone was stuck with "No Radio" on the boot loader screen and the SPL as "SPL-2.31.CoKe", but none of the 3.x ROMs would flash properly that I tried. So here are the steps that eventually recovered it (mostly...):
1.) I installed the ROM above from the tri-color screen (power+camera+reset). I still had no radio, but it was letting me past this and booting up to WM. http://forum.xda-developers.com/showthread.php?t=357762
2.) I then re-flashed the 2.31.CoKe boot loader (not sure if this step is necessary but listing what worked...)
3.) I tried to install RUU_Vogue_VZW_WWE_3.14.605.1_Radio_3.37.78_Ship.exe but it failed at 10% restarting to RUUNBH screen and the installer gave me Error [290]: Invalid Command
4.) I then tried to install the latest sprint ROM straight from the HTC site:_Touch by HTC (Sprint)_RUU_PPST_Vogue_SPRINT_WWE_3.03.651.4_2_Radio_3.42.30_AM_NV_2.04_Ship this looked like it was going to fail at the same part the Verizon rom did as it rebooted at 10% to RUUNBH screen, but the Sprint installer did something (I heard the computer lose and gain connection multiple times) and eventually it went right back and continued on from 11% and finished successfully.
5.) Rebooted and I had a radio now! Rather then risking trying to install the Verizon ROM again I went straight to the custom ROM I had originally started out with: NFSFAN 6.5 V6 which is working fine for me, except the GPS which is what started out my adventure of the last 3 days...
Just a note: for all flashes except the final one I simply waited till it was at the "Tap the screen..." stage till flashing. I never let any ROM but the final one run it's customization.
Click to expand...
Click to collapse
The above method works on a Vogue that is stuck on the bootloader screen with no radio.
Or if you get a rom to install and it stops at a windows screen that says no radio.
the only difference i tried was i didn't use the HTC Official Sprint rom, as i could not find it.
I used this rom.
RUU_Vogue_4350_ALLTEL_WWE_3.10.671.1_RS3.42.30_NV2.02_PRL30031_SHIP.exe
I let all customizations run on the last rom update.
I've made a mistake after a successful week following installing and running a custom ROM.
After Rooting the GT-I8160 a year ago and having no updates from Samsung since new it took me
a few days setting the phone up jumping from GB to CM11 so I didn't spot that ROOT access had been lost until this morning.
Tinkering with the internals didn't have the fear it held when first buying the phone on the Orange network in the UK
so I deleted Titanium Backup & Supersu but re-installing still left things un-rooted.
So I went straight to the original guide I followed on Cnets and rooted it again .... as I'd easily gained access to the ROM holding
down the 3 buttons manys times now and could do it again if I had trouble. ODIN carried out its job but when the phone restarted
it would get no further than the Splash screen Samsung Galaxy etc. In this position I tried to get it into Recovery mode keeping my
fingers on the buttons until it would turn off and restart, the only difference is when I try the Download mode the following appears
on screen;
Applying Multi-csc ........
Installing Multi-csc
Can't access to '/System/csc/EVR/system
Successfully applied Multi csc.
At the top of the screen it gives the option to Re-boot but again goes as far as Splash Screen where it remains.
I hope I've not killed the phone and that you can suggest how I can re-set it with the aid of Odin - the only access point.
:crying: Have I 'Bricked' it ...... put me out of my misery
Problem Resolved
After more investigating I saw a link recommending downloading the Firmware for Russia Ace 2 as it was the only one that whilst using ODIN
it had the files for PDA, Phone and CSC. After running this it got my phone up & running then from the same site - SamMobile I got the FW for UK & Orange which after 'wiping data/factory resets' brought my phone back to the day I'd purchased it. :victory:
Hope this may help anyone else who fears the end of their phone
As I understand you wanted flash CM11 on GB. If you want flash any custom rom above GB your baseband must be JellyBean. Just remeber
hello,
I have htc desire 816g dual sim octa core , last week its charging port burnt so i took it to repair shop to get it replaced
when it came back it was factory resetted , the phone had hundreds of photos nthat I didn't backed up , anyway I tried to recover the photos using many softwares wich asked for the phone to be rooted first , so eventually I did root it, and guess what? I could only get 5 photos back. anyway I mistakenly updated the OS and the update started normal and in the middle of the process it stopped and gave me the lying Andy and "error" word underneath I found later it is in the recovery mode... wiped cash ,factory reset and restart, nothing changed, installed a custom rom on sd and tried flashing, nothing too. installed android studio and tried to get to fastboot to unlock the phone .. I could get to fastboot but the command get oem identification token didnt give me a result wich suppose to be a number to get the phone unlocked via htcdev. now I'm stuck I spent the week trying to get it to work without any luck.
please help me, I emailed htc tech support but didnt get answer.
is there any repairing tool or something
any help would be strongly appreciated
for diagnosis purposes the phone now start stay on htc logo page for a minute and restart itself and go to the page that has the lying Andy and when i push the power button I see the recovery mood menue
Where did you buy the phone? Are you able to boot in hboot? Could you please post hboot data and getvar data?
Hi guys,
(Samsung S4 Mini GT-i9190)
I could really use some help.
I have been searching all over and perhaps I'm not understanding what is being said so if it sounds familiar and there is a solution then i'm thankful.
So about a week ago, the phone came back from repairs and had the motherboard replaced after the phone was washed by accident. Nonetheless, there hasn't been any hardware defects besides signal loss now and then.
When the phone came back, it had 4.2.2 and it automatically picked up the update to 4.4.2 which I did. The phone worked fine until 2 days ago, where it just stuck at the Samsung galaxy gt-i9190 screen and just freezes there.
I can boot into a custom recovery (Philz) (not stock recovery for some reason) and download mode. I then attempted to install CM 11.0 as I got frustrated. It worked, booted past animated logo and install the apps until i came to the language section where the touchscreen which didn't work (unresponsive). I then reverted back to the stock ROM found at sammobile (i9190xxxCOD2XFA - South Africa), loaded the custom recovery and still no booting past the first screen. The custom recovery touchscreen (Philz) is also non responsive (besides using the volume keys, home button and power for navigation).
I flashed a couple of times, nothing works.
Is there a root cause to these issues? The unresponsive screen, not booting properly?
Some info: KNOX is voided 0x1
Please help!! Thank you in advance
It's not „root“ that cause your problem. You should have to choose right recovery for your model. Flash back to original ROM and look for one of fully supported custom ROM here on the XDA and fallow all steps how to flash it properly. Succes ! Cheers !
Alright, I'll try that. What I did in the meantime was flash, Slimkat 4.4.4 UNOFFICIAL rom for I9190 (http://forum.xda-developers.com/showthread.php?t=2708677).
The rom booted into the andoird system but the touchscreen is still unresponsive.
@Boombastical .. If you can help me by giving me a guide in order to do what you say, then please do help. Even in recovery especially TWRP the touchscreen is unresponsive except for ClockWorkMod and Philz. So i don't know if it is hardware related or I'm doing something wrong.
Its driving me crazy :crying:
Update
So what I did last night:
I loaded the SlimKat rom and based on the stock bootloader and after doing a couple of battery pulls the screen starting functioning properly. However it was just luck or could've been something more technical.
I need help in understanding why that happened.
Then I decided I dont trust my method and reloaded the stock 4.4.2 firmware from sammobile. What then happened, is that it booted past the "Galaxy GT-I9190" screen into the samsung logo and then installed the applications. Come to the choose language screen, the touchscreen became once again unresponsive.
Bear in mind, that when I did a reboot with the stock rom, it didn't want to boot past the screen and just hung there.
So what could my problem be?
Is it the rom that I used? Using Unified Android Tool, I saw my region code is GB which I haven't seen anywhere in the stock roms.
Could the system somehow become corrupted? Emmc, partitions? Could the screen calibration be out of sync?
Must the bootloader always be the stock one? Are there custom bootloaders that one can use?
Please help, thanks
GeezyTab88 said:
So what I did last night:
I loaded the SlimKat rom and based on the stock bootloader and after doing a couple of battery pulls the screen starting functioning properly. However it was just luck or could've been something more technical.
I need help in understanding why that happened.
Then I decided I dont trust my method and reloaded the stock 4.4.2 firmware from sammobile. What then happened, is that it booted past the "Galaxy GT-I9190" screen into the samsung logo and then installed the applications. Come to the choose language screen, the touchscreen became once again unresponsive.
Bear in mind, that when I did a reboot with the stock rom, it didn't want to boot past the screen and just hung there.
So what could my problem be?
Is it the rom that I used? Using Unified Android Tool, I saw my region code is GB which I haven't seen anywhere in the stock roms.
Could the system somehow become corrupted? Emmc, partitions? Could the screen calibration be out of sync?
Must the bootloader always be the stock one? Are there custom bootloaders that one can use?
Please help, thanks
Click to expand...
Click to collapse
Possible solution:
So I thought it could be screen calibration so this is what I did to make my phone work.
I loaded the CARBON Rom as I somehow lost root privileges with SlimKat. It loaded into the OS as per normal but the touch screen didn't work. So after numerous battery pulls, i read this post http://forum.xda-developers.com/showthread.php?t=2353972&page=1 .
So then I connected the phone to the pc (having had the samsung drivers installed as well as adb) and booted into cmd promt as admin.
This is what I did in cmd prompt:
cd adb
adb shell (make sure there is a "#" as that ensures you that your phone is rooted)
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
@xcxa23
It then still didn't work (the touch screen) then somewhere on one of the pages in the above post, someone mentioned holding home button. I switched the phone off, I then held the home button (until it booted into the OS) and then powered the phone on. The phone booted into the OS and presto the screen worked again. I did a reboot and the screen is still fine.
Again I'm not sure if its that exact method but what I am sure of, is that I did a clean rom install (an option in Philz touch recovery), wiped the cache, formatted the options (boot, system, cache, preload, data) in mounts and storage and then proceeded to install the rom from the sd card.
I haven't tried with the stock rom as yet so if this helps you, goodluck and if you can help improve on this method or help me understand why this is happening, it would also be appreciated.
Thanks
Confirmed for that is
GeezyTab88 said:
Possible solution:
So I thought it could be screen calibration so this is what I did to make my phone work.
I loaded the CARBON Rom as I somehow lost root privileges with SlimKat. It loaded into the OS as per normal but the touch screen didn't work. So after numerous battery pulls, i read this post http://forum.xda-developers.com/showthread.php?t=2353972&page=1 .
So then I connected the phone to the pc (having had the samsung drivers installed as well as adb) and booted into cmd promt as admin.
This is what I did in cmd prompt:
cd adb
adb shell (make sure there is a "#" as that ensures you that your phone is rooted)
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
@xcxa23
It then still didn't work (the touch screen) then somewhere on one of the pages in the above post, someone mentioned holding home button. I switched the phone off, I then held the home button (until it booted into the OS) and then powered the phone on. The phone booted into the OS and presto the screen worked again. I did a reboot and the screen is still fine.
Again I'm not sure if its that exact method but what I am sure of, is that I did a clean rom install (an option in Philz touch recovery), wiped the cache, formatted the options (boot, system, cache, preload, data) in mounts and storage and then proceeded to install the rom from the sd card.
I haven't tried with the stock rom as yet so if this helps you, goodluck and if you can help improve on this method or help me understand why this is happening, it would also be appreciated.
Thanks
Click to expand...
Click to collapse
Hey guys, just a quick update.
I reloaded Cyanogenmod mod CM13. I can confirm that my screen didn't freeze up and booted perfectly. I also then decided to take a chance adn reload the stock rom 4.4.2 and it also worked perfectly and booted directly into the OS.
I'm guessing the screen calibration was out.
So if this happens to you, I would suggest loading a custom rom and doing the screen calibration reset through adb and then test again with another custom rom. Once you comfortable, you can reload a stock rom.
I used Philz Touch for recovery
Thanks to everyone who put posts up .. Time to rest
Not working again!!
Hey,
So in my previous post I said I got it to work. Well I did, up until a few minutes ago when the phone just decided to freeze up again. I restarted the phone and would you know, back to square one!
I've noticed issues that I'm wondering if they could be the problem:
1) The audio didn't work at all. By audio, I mean the mic. When I did voice recording, it just gave static, whatsapp calls, the other person can't hear you as well as regular phone calls.
2) I just rooted the phone in order to change the audio_policy.cnf and delete lines relating to the above audio problem but then the screen, return, and menu button didn't function. The screen could still rotate until I pressed the power button to lock then unlock and then it didn't unlock :crying:
So once again, some help guys please. Is it rom related, hardware (motherboard, chip) or software that just isn't working right? Could it be KNOX?
Thanks
I own a canvas A1 4GB variant, I had rooted my phone and flashed custom recovery, After my phone's battery started giving me problems(lasted only few hours), I considered flashing Stock ROM or any other trusted ROM, I had flashed RR M[07/07] based on android MM, The battery was still giving problem, A week later, My mom's phone broke and she had to use this(A1) temporarily, I formatted everything and thought of flashing stock ROM and handing over the phone to her, I tried flashing the official zip via TWRP, It gave me some error regarding Memory couldn't be created, System partions or something(I don't remember). And after that, I could't flash any ROM, I experimented out some settings in TWRP and now my phone is totally dead, It does not boot up at all, No recovery mode turns on, Nothing except a black dead screen, I tried flashing stock firmware via SP flash tool, It completes and says successful but still nothing happens, Just wanna know if something can happen to this one? I really loved that device and would be great to have it back working.
Every android one is dead...now iam suspicious about google and micromax because it's their trick
mithunpk said:
Every android one is dead...now iam suspicious about google and micromax because it's their trick
Click to expand...
Click to collapse
Is it? I doubt you, How is that possible?
singhaman1 said:
Is it? I doubt you, How is that possible?
Click to expand...
Click to collapse
My canvas a1 and my two other friends android one phones (same Micromax ) died in the same way