Develop Bugs

Phone screwed ? Can't mount SD / emergency calls only

Ok, where to begin:
I Rooted this weekend and have been installing a few roms, all has been fine. This afternoon I tried to partition a fresh SDcard using the windows-recover.bat method to allow apps2sd and that (I believe) is where it all went wrong.
When I rebooted the phone it went into a boot loop, never getting past the HTC logo.
So I factory reset from the HBOOT menu and it still looped, until I put a new SD card in - then it loads ok (I'm using Defrost 2.41d) but after the initial set up it says emergency calls only - I manually select Orange (the phone is a factory unbranded/unlocked CPW handset) - it says it's not allowed to connect - won't connect using my T-Mobile sim either.
It also says the SDcard isn't mounted no matter what SDcard I try (tried 4x).
I've tried booting into recovery and installing a zip from the SDcard so try and install a new ROM and it fails saying unable to mount SDcard.
I have also done a cache wipe, and basically any other option that sounds like a wipe type option from within the Recovery menu on HBOOT/Clockword MOD.
I'm lost, if I can't access the SDcard in any way then I'm screwed and can't reflash.
Any ideas gratefully received...

have you tried pushing a rom to the phone from your computer? or unrooting with an official HTC RUU ROM and starting again?
also search the "USB bricked" stuff on the desire android development forum...

Thanks for the advice
I'm trying to push a std Official ROM but the PC just doesn't see there is a phone attached when the phone is in normal use mode, it starts to see it in HBOOT mode but then says the driver has failed etc.
Someone elsewhere has mentioned the USB brick possibility but from what little I've read it requies SDcard functionality and my phone just doesn't see ANY SDcard - even in HBOOT / Clockword MOD recovery mode.

any feedback?
could you solve the problem?

Failed Root; Stuck in Loop "process com.google.process.gapps has stopped"

Hello and thank you for taking time to read this post.
I attempted to root my At&t Samsung Galaxy S3 today then install tha AOKP Rom, and it back fired due to poor instruction, and poor execution. At the moment my phone, whenever it turns on "inititing swager" (with a pink horse and gears) then gives me a pop-up saying "Unfortunatly the process com.google.process.gapps has been stopped." and "Unfortunately, Setup Wizard has stopped". Whenever I hit ok, the other shows up. I have access to the pull down menu, but can't open any of the links on it. I can also shut it off then get back to the root(hat menu) menu. From which I have tried the option "wipe data/Factory Reset" link, but that changes nothing when I reboot. At this point I am just looking for a way to get it back to factory settings or at least working!
How I got here:
1. Rooted the phone through my computer (successfully it seemed)
-Using this tutorial: /watch?v=bIUA1IxiJzo
2.Started puting AOPK on!
(with this: /watch?v=qzcR-G7EKSw
Look, I know none of you have to help me but any feedback will be greatly appreciated.
P.S. I hav looked through other forums about the gapps error, but the difference is mine is not running to the home screen so I can't go to application manager!

Two suggestions:
1) Put your phone in recovery mode (i.e. where you can do factory resets from), transfer a different ROM image over to the device (I'd use adb to do that from recovery mode), flash it, clear data/cache/etc., reboot the phone, and hope it works.
2) Put the phone in download mode (Vol Down + Home + Power; just like entering recovery, but Vol Down instead of Vol Up), and use Odin to flash a rooted stock image as detailed here; put CWM / TWRP / whatever recovery you want to use on the phone again, and get back to flashing ROM images from there.
In the future, try to be careful of what ROMs you flash... not everything works very well, as you've just discovered.

Thank you for responding so quickly! I am attempting the first method, however i am not sure how to transfer a different rom image(im assuming the adb stands for Android Debug Bridge). I was using the internal SD, but I can plug it the phone into my computer, and it says no drivers found for this device, where before it recognized the phone. Once I get that I can clear the other data and restart.
Your help is very appreciated!
smelenchuk said:
Two suggestions:
1) Put your phone in recovery mode (i.e. where you can do factory resets from), transfer a different ROM image over to the device (I'd use adb to do that from recovery mode), flash it, clear data/cache/etc., reboot the phone, and hope it works.
2) Put the phone in download mode (Vol Down + Home + Power; just like entering recovery, but Vol Down instead of Vol Up), and use Odin to flash a rooted stock image as detailed here; put CWM / TWRP / whatever recovery you want to use on the phone again, and get back to flashing ROM images from there.
In the future, try to be careful of what ROMs you flash... not everything works very well, as you've just discovered.
Click to expand...
Click to collapse

Gapps loop
How can I post a doubt in XDA forum?

What custom recovery is on your phone? I suggest installing Philz Touch via Odin if possible and then flash a new rom from an external SD card.

Galaxy Note 8 (GT-N5110) PC Connection Problems - Boot Loop - SOLVED by ME

NO ONE?????
ODIN --> Flash Stock Recovery (AP) with NAND Erase All Option Checked (because it seemed to make sense) + Auto Reboot + F. Time Reset --> Reboots to Stock Recovery (did not work before) --> Reboot into Recovery --> Wipe Data/Cache and Dalvik just to be safe (this crashed it before) --> Reboot. THE END
TL/DR: I am currently stuck on recovery/update mode. Any attempt to wipe data or clear dalvik crashes it. any attempt to access data through TWRP crashes it. Flashing stock rom or custom rom does not help. Somethings wrong with /data? It thinks it has root from the CF Auto Root, but does not really? Something wrong with partitions? Should I wipe the nand with ODIN 3.10? Repartition? ugh ... Please help ...
I have searched the forums and found nothing that describes this issue precisely. I have also tried to apply various suggestions to repair, which, for the most part seems to have made it worse. I am hoping that people still look at this forum.
PC - Windows 7
Initially @4.2.2 ---> Touchwiz debloated stock ROM which I rooted. It worked for a couple years, but the device crashed frequently. I do not recall much about the installation, but believe that I used CWM/TWRP at the time. After installing the ROM, I ran triangle away (out of the box, it had 4.1.2, i recall)
I decided to upgrade to the most recent stock ROM (4.4.2). In order to do so, I used an easy installer I found else where on XDA. (http://forum.xda-developers.com/showthread.php?t=2773712 ---ODIN One Click exe). The device was not initially recognized, so I reinstalled the official driver package (said that they already existed, but I installed again anyway). Ran 1-click and it appeared to work.
Initially, the device booted (long startup) and seemed to function. It also preserved all data and programs (presumably did not touch the internal memory - 16 GB) and possibly root /data.
I then tried to root through most recent ODIN with CF auto root. This appeared to work and rebooted (again, showing the updating android apps screen before fully booting).
The only thing that i could find that had changed was the wallpaper (showed on lock screen but not on home screen). I could no longer find the image, so tried to go to /data/data to find it with root explorer equivalent. This is where it started to act weird.
NOTE: I did not clear anything (system cache, etc. at any point)<--a lie (see below)
It showed the root folder fine, but when I clicked on /data it took a while and could not access it. It either rebooted itself or I rebooted, but this time it was stuck in a boot logo loop. I entered download mode and flashed TWRP through ODIN. I set it to not reboot automatically so that the bootloader was not overwritten automatically (thus losing recovery). TWRP came up. The computer recognized it as a Media Device after I mounted USB storage. Just in case, I copied all of the important files from the internal SD Card to my computer. I then tried to go to the file explorer to copy the wall paper and it forced a reboot. At this point it was stuck on a logo screen boot loop again. I was able to enter Download mode and reflash TWRP. This allowed me to enter recovery again, however, now it would only boot directly into recovery (or Download mode if I did the button combo). The interesting thing was that it would reboot two or three times before successfully entering TWRP.
I believe I tried to reflash the stock ROM at this point, which might have worked but made no difference.
I was also having a lot of problems getting Windows to properly recognize the device. I had to reinstall the drivers a couple times. I tried Kies after the problems started and it tried to connect by failed. The diagnose connection did not work either. I was not able to get Kies to connect though I tried several times throughout the attempted repair
I downloaded a stock-rooted 4.4.2 ROM from here and tried to flash it. It failed.
I also tried to flash via Heimdall, but initially could not find any stock ROMs for Heimdall for the Galaxy 8. (The driver utility that is included helped to get the phone recognized by Windows sporadically).
I decided to switch over to CWM touch recovery, which I flashed via ODIN (I was having issues with TWRP again and also could not get windows to recognize the device as a media device when I mounted USB storage). This worked after a couple tries and I was able to enter CWM. I attempted to flash the stock ROM but it failed. Either at that point or when I tried to mount data it returned an error that device did not have root. Again, it would only boot into CWM (on its own) or Download mode (with key combo). At some point around here I cleared the cache and dalvik (error) after it returned an error saying insufficient space when trying to flash ROM.
I dissected the .exe from the autoflash used in the beginning (stock unrooted 4.4.2) and used the contents (system.img, cache.img, hidden.img, tz.img, recovery.img and one other I do not remember) in Heimdall to create a Heimdall package. At this point I figured out I did not need to create the package, but just specify the individual files. I flashed. It appeared to complete System.img successfully and then failed. Tried again with the same result.
Now when I rebooted, it would enter download mode with the Key combo, but otherwise it booted instantly to an error screen to the effect that a firmware installation had failed and to use the repair function in Kies to fix. Kies still did not recognize it.
At this point, I figured I should stop. Currently I can get to the download screen or the error screen. The computer recognizes it but intermittently fails to install driver. Zadig.exe sees it as Gadget Serial. Sometimes Windows just sees it as SAMSUNG_Android, in which case drivers fail. Once or twice I got it to recognize it as Samsung USB Composite Device, but Kies would still not work.
That's all i have for now. If more information is needed, let me know and I will update the post when I get home from work tonight (this is from memory).
Thank you
UPDATE: last night I went home and was able to get it back to the point where I could flash TWRP or CWM recovery. If I try to flash Stock Recovery, it fails. A minor problem is that I cannot turn it off - it just turns it self on again, so the battery keeps running down.

Made an stupid error when flashing my phone - help needed eventually

Hi,
have to say it was my first try ever to flash a phone.
I've followed the ReadMe-Thread to the letter and with a little bit of try&error I got it done smoothely until I came to flashing the CustomRom "lineage-18.1-20210311-UNOFFICIAL-hima".
The instruction is " Choose "Wipe" and wipe everything except for "Micro SDcard", "USB-OTG" and "SD-Ext" via the advanced wipe. ".
What I did was exactly the opposite. I did mark "Micro SDcard", "USB-OTG" and "SD-Ext" and wiped it. There was an error message but as I was shocked about my mistake I can not remember any detail.
I've done it the right way after this error without booting the device and as far as I see it the flash was successful. The phone now starts Lineage and seems to work. Not sure yet as I have not got a new prepaid SIM but it's underway already. But the "rest" of it works. Have installed some apps with adb already.
BUT: It seems as I have destroyed the recovery mode at least. When I try to boot into recovery I only get a normal boot into LineageOS. Means that I start to bootloader mode and then select "Boot to recovery" the screen becomes black and then after some time the LineageOS starts. I can also switch between download ans bootloader mode but can not reach recovery.
AND the htc_fastboot command does not have any effect, will say NO devices are visible.
May someone in the know please enlighten me what I've done and how I may eventually recover the recovery mode?
Thank you very much for reading this and if I've written absolute nonsense here please bear with me, I'm German.

I guess you can flash custom recovery again using fastboot and reinstall Lineage!

Thanks.
When I try to use htc_fastboot there is no reaction and "htc_fastboot devices" shows nothing.

Same problem with me. to negligence, i didn't do this " "Wipe" and wipe everything except for "Micro SDcard", "USB-OTG" and "SD-Ext" via the advanced wipe" and installed the lineage 18.1. and now I don't have Recovery and the phone boot to lineage os but it will not boot totally. it will shut down and then boot again. (loop)
please help me.
I can boot to download mode
unlocked
s-on
Os-4.28.401.3
any help is much appreciated. thank you in advance

Hello,
I have a similar problem. It is an m9 with an unblocked bootloader. I got it from a colleague.
It had a cyanogen mod and TWRP on it. I set the cyandogen mod to factory settings and then activated the developer options so that I can boot directly into the recovery from the operating system.
It also worked perfectly. Then I wanted to update TWRP with the TWRP app.
It worked until I was asked whether I wanted to flash TWRP into the recovery or into the boot.
I chose recovery and thus rendered the phone unusable. It only boots into the bootloader or into download mode.
My attempts to flash a stockrom via adb or an executable file on a windows pc failed.
With the latter, the smartphone at least responds via the usb port. But so far I have not found the right RUU file for the phone.
Unfortunately, it also does not respond to 0PJAIMG.zip files on an sdcard formatted with FAT32.
Is there a way to force-flash TWRP onto the phone?
Many greetings
Draal

A5 2017 (SM-A520F) bricked after TWRP wipe before installing custom ROM

Hi!
So it appears I have soft-bricked my phone. At least I hope this is a soft one, but looks harder and harder with every minute.
What I did:
- I have an A5 2017 initially running Android 8.0.0 build A520FXXUGCTKA.
My plan was to install Lineage for MicroG on it. I followed the instructions on the Lineage website, encountered immediately an absence of OEM unlock button, solved it with flashing latest stock ROM with CSE which also reset the device and doing the date/time trick (+- 8 days), after which OEM unlock appeared and I had both it and USB debugging on.
So I proceeded to install TWRP and was able to successfully boot into it, after which I followed the next fatal steps:
Now tap Wipe. <<did this
Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage. <<did this, and it suddenly gave me a bunch of errors about being "unable to mount /data"
I disliked this and decided that I have to solve this before proceeding to step 3 of the guide. So I found somewhere a solution to go to Advanced Wipe, select the Data partition and repair it, which I did, but after this step I think it recommended to reboot the phone, which I unfortunately did... and I was stuck in Samsung boot with only the logo loading. I panicked and immediately tried to go back to recovery, which stopped the loop and game me the red message Only officially released binaries are allowed to be flashed.
So the status of the phone right now is:
- I cannot go into recovery mode anymore. It gives the red message about official binaries.
- Phone doesn't load into system either. It again gives the red message.
- I can go into Download mode and see the following status:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-A520F
CURRENT BINARY: CUSTOM
( I did not actually go to step 3 of the guide and try to upload the custom ROM. But I suspect this is because it now sees the ROM as changed/damaged)
SYSTEM STATUS: Official
RMM STATE: Prenormal
(This line was absent when I managed to turn on the OEM unlock finally. Now it's back)
FRP LOCK: OFF
Secure Download: Enabled
- I cannot upload ROMs via Odin anymore. The device isn't seen by it with Download mode like before. The drivers were installed by me previously and I was able to upload via Odin. I tried to reinstall them with zadig, but instead of 2 entried named Gadget Serial like before, zadig now only sees one Gadget serial and one Unknown device #1.
I tried to flash ROM in parts to the partitions directly (binaries, img) via Heimdall (using phone.pit mapping I downloaded a bit earlier via Heimdall). Heimdall said that it was a success on each download part, but also wrote 0% near the progress and it seems that it did nothing.
To me, phone looks now as if it sees its ROM as damaged, but ignores any attempts to get anything on it anymore. Which is logical because it seems to have either locked itself in a new state or restored to the state where the USB debugging and OEM unlock are not turned on. And I can't obviously get the system to load to turn them on.
Maybe somebody encountered a similar situation and knows how to get it out of this state or what this might be?