Hello, sorry for creating a 'HELP I don't know what to do!' thread, but I really am stuck now.
I had some Adrenaline rom for quite a while but today I decided to go back to stock because I was having some minor problems.
I suppose flashing stock went okay. I've got the stock recovery now, but the phone loops on boot. With the help of this thread I've figured this is because the previous rom (probably) used ext4 whereas stock needs rfs. That guy got it working by going through adb doing something that I can't even get to because adb doesn't recognize my phone. (I've tried installing drivers for adb but Windows doesn't want to use them because it thinks its own drivers are superior, even though I've uninstalled these, it keeps reinstalling them)
I also can't get CWM working. I've run the root update.zip and that seemed to go fine, but when installing CWM the screen just freezes and the phone reboots when pressing the home button.
I'm kind of stuck on how to revive my gio, any help is greatly appreciated.
Thanks.
Edit: SOLVED, thread may be deleted. Went to try flashing CWM through odin (ext4+rfs) and during the reboot phase my phone suddenly booted into the android OS.
Hello there good folks of XDA,
I'm at work right now and my phone is at home but here is the story of what went down last night.
I tried to root my phone, after installing TWRP and superuser I ran a root-check app and it said that I was not rooted, so not thinking I tried the 'fix permissions' function of TWRP and then everything went haywire.
It's an international version M8 that I've had rooted before but reverted back to stock to get the lollipop OTA updateBy haywire I mean the phone booted up but no widgets displayed and most of the apps still appeared in the app drawer but nothing would open.
Instead of seeking help at this point I went to town on trying various things :silly:
The last of which was try and flash a boot image to it, but I think I must've used the wrong one as after doing that it's now stuck in a boot into TWRP loop.
From when I had previously rooted the phone I had a boot image (I think) 2.22.401, it matched version on the recovery file I used when reverting to stock in the past so I thought it would be fine
I've still got a terminal open at home with all the results of the fastboot getvar all command but from memory my CID was HTC_044
Can someone help outline the process and possibly even the files I need to reflash my phone into a working order. (it doesn't need to be 'stock' but that would be best)
I use a mac by default but I do have a windows machine at the ready I can use so feel free to base any tips on doing it from either platform
Post the getvar all output, minus IMEI and serial number, and we'll go from there
Thanks for coming to my assistance but in the end (after a few more slight failures) I managed solve the problems myself.
I believe that my first problem was using a not up-to-date version of TWRP (2.7) with Lollipop; the first symptom was my attempt at rooting my phone, the process appeared to go well but just wasn't working properly.
My second problem was 'fixing permissions'; after doing that my phone went totally haywire and while it would boot into android nothing would work properly
After going to a previously used stock recovery and getting nowhere I went back to the same TWRP I started this with and still had fixed nothing.
at this point I did a factory reset from the recovery mode and while that got me booting back into android I was being swamped with error messages and couldn't get past setup wizard crashing.
At this point I flashed the wrong boot image and had a nearly impossible time getting to the system boot menu instead of TWRP being what it always went to. Eventually I must've got the timing right with the buttons or something because I got back into the system boot menu and could access fastboot.
Once in fastboot I downloaded a full nandroid backup and restored it, my phone was working again... or so I thought, it was still suffering from permissions problems
at this point I re-rooted it with the latest TWRP, got SuperSU working properly, did the 'restorecon' command with a terminal app and now the app crashes I was getting have stopped and I can see and write to the phone memory.
After trying to test everything I could think of on my phone today I think it's finally fixed.
I tried to do a partial/selective app+data restore from a nandroid backup I took of my own phone just after the 'fix permissions' event but it didn't work properly so in the end I manually re-setup my phone. I do run an sms backup app so overall I only lost time...
Hi guys – hoping you can help me following an issue with my M9 I bought a couple of days ago. Last night I unlocked the bootloader with HTC dev, rooted with TWRP/SuperSU, S-OFF’ed with SunShine, updated firmware to 1.40.401.5 per matanlevanon‘s thread, then flashed MaximusHD.
Up until the last step, everything went well – but I’m now stuck in boot loops. I can currently access both Download Mode and bootloader; but trying to launch recovery gets as far as the TWRP splash screen before my phone reboots again.
I've reflashed TWRP.img using fastboot; but when rebooting into recovery I still have the same result (TWRP splash screen before my phone reboots again)
I've also lost ABD - in Download Mode/bootloader, Windows Device Manager see’s my phone without issue and correct drivers – but ADB server doesn’t recognise my phone.
I’ve tried everything from HTC Sync bundled drivers, PdaNet drivers to generic ADB drivers – but ADB seems to refuse to see my phone regardless of what I try.
Seemingly if I can get a working recovery image / TWRP on and working I can wipe and try to flash again, but current images don't seem to be helping. Any suggestions / help please?
Got it, cache partition was corrupted! fastboot erase cache let me get back into TWRP and reflash my ROM.
Fingers crossed it's smooth sailing from here
Hello.
The other night I applied 3 software updates to Android and ended up with an unusable phone. The updates (I assume) were like this: http://forum.xda-developers.com/tmobile-htc-one-m8/help/3-software-updates-t3268014
After the phone rebooted a couple times, it got stuck at the white HTC logo screen (I ended up falling asleep and the phone was like the after waking up, so stuck for about 6 hours) and wouldn't respond to just holding the power button. I had to hold power + vol up to get it to restart. After restarting it now boots to a black screen. It is possible to get to HBOOT and TWRP but I can't get adb to recognize it anymore so I'm not sure how to go about getting fixes on the phone.
The phone was running a custom recovery (clockwork recovery) and rooted. I then tried to get it back to stock to apply the Android 5.0 RUU and then used TWRP without flashing the recovery to root the phone again. My guess is that something about that process might have messed with something that one of the software updates was updating.
So, I have two questions:
1. Is it possible to recover files (pictures, for exampl) off the internal sd? Like I said, I cannot get adb (or windows) to recognize the phone, though it does show in the windows device manager.
2. If it's not possible to get recover those files, how can I get the phone usable at all?
Can you get it into the boot loader?
Yes, luckily I can get to the bootloader.
hatbocs said:
Yes, luckily I can get to the bootloader.
Click to expand...
Click to collapse
If so once in the bootloader can you use something like:
fastboot boot twrp-2.8.7.0.img
to boot into twrp? (note twrp-2.8.7.0.img is the filename of the twrp image that I saved it as, yours might be different)
If you can boot into twrp then you can install a rom/backup. also you could use, I think, something like "fastboot flash recovery twrp-2.8.7.0.img" as well.
-brad
I'm at work so I can't test this again to make 100% sure but if fastboot works like ADB then my phone doesn't show.
I do currently have TWRP installed however windows does not see the phone.
So if twrp works, you should be able to use that to connect to your pc. If not go and buy an OTG usb drive. Copy a Rom onto it, and then connect it to your phone. One time I messed my phone up and I used this method.
Worth a try. I'm in the middle of moving and that box of stuff isn't in this house. So I'll have to wait to report back. Thanks for the help so far.
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