Develop Bugs

[help] stuck at boot animation

Hello everybody I have an Sony Xperia Arc S (LT18i), I come from HTC,Samsung and Kindle Fire so I'm new with Sony devices.
The Arc S is a second-hand from my brother, I thought I would give it an ICS ROM so I flashed FXP 133 CM9 and it works great without any problem (with flashing), but it wasn't as smooth as I wanted it to be and I don't want to use a buggy CM10 yet.
So I did some research and I found a reply somewhere that flashing the CM9 Baseband 72 would make the ROM smoother, so I flash Baseband 72 via FlashTool and then it won't go pass the boot animation. I thought that maybe the ROM corrupted and so I flash CM9 Stable ROM and Kernel but it's still the same, stuck at CM9's boot animation, and I wiped it clean before flashing
I know you're suppose to wait a while in first boot, but it's 20 minutes and still no boot, I can put it to fastboot,flash mode and CWM, but if you can't power it on, you can't flash it with FlashTool right? And I can't charge it, whenever I plug my Arc in the charger, it boots to the bootanimation and stuck there again.
I doubt it's something wrong with the partition or whatever it is cuz' CWM gives me "no MTD partition: userdata" and "no app2sd partition found"
Conclusion: I can't flash a firmware (maybe cuz' I can't power it on, hope there is another way) but flashing a ROM or Kernel just won't work, right now I'm plugging my charger in but still the CyanogenMod man is looking at me.
HELP NEEDED! PLEASE!

pmdisawesome said:
Hello everybody I have an Sony Xperia Arc S (LT18i), I come from HTC,Samsung and Kindle Fire so I'm new with Sony devices.
The Arc S is a second-hand from my brother, I thought I would give it an ICS ROM so I flashed FXP 133 CM9 and it works great without any problem (with flashing), but it wasn't as smooth as I wanted it to be and I don't want to use a buggy CM10 yet.
So I did some research and I found a reply somewhere that flashing the CM9 Baseband 72 would make the ROM smoother, so I flash Baseband 72 via FlashTool and then it won't go pass the boot animation. I thought that maybe the ROM corrupted and so I flash CM9 Stable ROM and Kernel but it's still the same, stuck at CM9's boot animation, and I wiped it clean before flashing
I know you're suppose to wait a while in first boot, but it's 20 minutes and still no boot, I can put it to fastboot,flash mode and CWM, but if you can't power it on, you can't flash it with FlashTool right? And I can't charge it, whenever I plug my Arc in the charger, it boots to the bootanimation and stuck there again.
I doubt it's something wrong with the partition or whatever it is cuz' CWM gives me "no MTD partition: userdata" and "no app2sd partition found"
Conclusion: I can't flash a firmware (maybe cuz' I can't power it on, hope there is another way) but flashing a ROM or Kernel just won't work, right now I'm plugging my charger in but still the CyanogenMod man is looking at me.
HELP NEEDED! PLEASE!
Click to expand...
Click to collapse
now I am guiding to you an almost new territory here but try this :
Download JJ hybrid 3.2 stable from here : http://forum.xda-developers.com/showthread.php?t=1535971
Download ICS stock recovery kernel from here : http://www.mediafire.com/?t75gje77zciea6x
Remove your SD card..read it through a card reader and extract the jj hybrid stable zip and copy the extracted folder into \clockworkmod\backup
Now put SD card back into the phone and keep the phone turned off
Keep the Menu button(the right most button) pressed while attaching the USB cable to the phone. No need to turn the phone on. U will notice a blue led light on the side of the phone. it means the phone has been connected into the fastboot mode.
Open the flashtool. Let it identify the phone. Then click on the lightning icon on top and choose 'fastboot mode'
On the next screen click on 'select kernel to flash'
Direct the browse screen to the ICS stock recovery kernel which u downloaded.
Once its done in a few seconds, remove the usb cable and turn on the phone.
As soon as u see the SONY logo press volume key down to enter into CWM
Wipe data, wipe cache, wipe dalvik
Then go into backup and restore >> restore >> choose the folder you had copied which should be there.
reboot when done..it would flash JJ hybrid on your phone which is a good enough ROM..but if you need CM9 you can proceed after that..Atleast you have a restore now to get back to normal in case something goes wrong..

iwarind said:
now I am guiding to you an almost new territory here but try this :
Download JJ hybrid 3.2 stable from here : http://forum.xda-developers.com/showthread.php?t=1535971
Download ICS stock recovery kernel from here : http://www.mediafire.com/?t75gje77zciea6x
Remove your SD card..read it through a card reader and extract the jj hybrid stable zip and copy the extracted folder into \clockworkmod\backup
Now put SD card back into the phone and keep the phone turned off
Keep the Menu button(the right most button) pressed while attaching the USB cable to the phone. No need to turn the phone on. U will notice a blue led light on the side of the phone. it means the phone has been connected into the fastboot mode.
Open the flashtool. Let it identify the phone. Then click on the lightning icon on top and choose 'fastboot mode'
On the next screen click on 'select kernel to flash'
Direct the browse screen to the ICS stock recovery kernel which u downloaded.
Once its done in a few seconds, remove the usb cable and turn on the phone.
As soon as u see the SONY logo press volume key down to enter into CWM
Wipe data, wipe cache, wipe dalvik
Then go into backup and restore >> restore >> choose the folder you had copied which should be there.
reboot when done..it would flash JJ hybrid on your phone which is a good enough ROM..but if you need CM9 you can proceed after that..Atleast you have a restore now to get back to normal in case something goes wrong..
Click to expand...
Click to collapse
Thanks, it works. Now my Arc is alive again
Sent from my YP-G70 using xda app-developers app

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.

After root and install a recovery flash, my phone won't work

I rooted my phone using kingroot apk. Since the kingroot apk did't install a recovery flash boot, i install the TWRP recovery using XZDualRecovery for Sony Xperia Z1 Compact. It worked. I can finally open the TWRP recovery flash boot. I installed an Xposed zip file using the recovery boot. After the installation finished, i try to reboot my phone (using an 'system' option on the recovery boot) but then, the problem started to happen. My phone remains on the very very first state "SONY XPERIA" thing. And it started to vibrate twice with the light turned green (and when i press the volume down key it turned purple and entered the recovery flash boot window). But, if i didn't press the volume down button, it will go to the next state "Powered by android". And a few seconds later, it rebooted to the first state. And the same condition keeps recur. I have tried to wipe data and did a factory reset (from the TWRP recovery boot ofc). Then i press a system reboot, but then an option appeared "Do you want to install SuperSU?" I clicked yes. And it began to reboot. And it stucked on the first state "SONY XPERIA". It didn't vibrate anymore, and the light didn't turn on anymore. But, the phone also did't go to the second state. I tried to use the "emergency" power off button. Then i turned the phone again. But it remained on the same occurrence.
What should i do?

hyemun01 said:
I rooted my phone using kingroot apk. Since the kingroot apk did't install a recovery flash boot, i install the TWRP recovery using XZDualRecovery for Sony Xperia Z1 Compact. It worked. I can finally open the TWRP recovery flash boot. I installed an Xposed zip file using the recovery boot. After the installation finished, i try to reboot my phone (using an 'system' option on the recovery boot) but then, the problem started to happen. My phone remains on the very very first state "SONY XPERIA" thing. And it started to vibrate twice with the light turned green (and when i press the volume down key it turned purple and entered the recovery flash boot window). But, if i didn't press the volume down button, it will go to the next state "Powered by android". And a few seconds later, it rebooted to the first state. And the same condition keeps recur. I have tried to wipe data and did a factory reset (from the TWRP recovery boot ofc). Then i press a system reboot, but then an option appeared "Do you want to install SuperSU?" I clicked yes. And it began to reboot. And it stucked on the first state "SONY XPERIA". It didn't vibrate anymore, and the light didn't turn on anymore. But, the phone also did't go to the second state. I tried to use the "emergency" power off button. Then i turned the phone again. But it remained on the same occurrence.
What should i do?
Click to expand...
Click to collapse
Possibly the wrong Xposed file. What you need is a clean /system. You can do it with flashtool. Or, since you can access recovery, you could use pc to copy a rom or prf on to your SD card, and flash through recovery. Have you used flashtool before?

Mi Max 3 stuck in fastboot

Long story short, I tried to flash a global ROM on my Mi phone. However, after a few unsuccessful attempts at doing so, my phone is now stuck in the fast boot screen.
I tried all I know and what I can find online, but the problem still persists, where when holding the power button it would boot to main power screen and then make a buzz and go back to the fastboot screen.
Have tried:
- Resetting through recovery mode (pow + vol up)
- plugging phone into my computer to reflash the ROM (error remote: unknown command) / on my phone it would switch out of fastboot and instead display this message: "press any key/button to shutdown"
- pow + vol down (held for more than 1 minute)
- pow (held for more than 5 minutes, everytime it would boot and then boot back into fastboot mode with the buzz in between)
- ADB console commands:
- fastboot reboot
- fastboot device
- tried using MiPCSuite, plugged my phone in, but application didn't detect my phone
- running all applicable applications as mentioned above as admin
- when resetting phone progress bar would stop at 1.03% then it would say reset completed (I don't think did reset the phone, but whatever...)
- tried different ROM versions, Global and China (Once again it would either switch out of fastboot on screen OR in the flash tool it would display the error "unknown command" which I assume would be something to do with the communication between my PC and the device itself)
At this point I don't know what else to do, watched every tut on youtube, read pretty much all the forums I could find related to this issue.
Any help would be much appreciated!

Is it locked or unlocked?
I whould try to update firmware, then recovery (wipe all at this point) and at the end ROM (format data, wipe dalvik and cache at this point), always worked for me. But - the phone should be unlocked for this

Wywern.pl said:
Is it locked or unlocked?
I whould try to update firmware, then recovery (wipe all at this point) and at the end ROM (format data, wipe dalvik and cache at this point), always worked for me. But - the phone should be unlocked for this
Click to expand...
Click to collapse
I have tried going into recovery mode and wiping all data, and trying to update the firmware via the flash tool. But as I said above I can't it gives me the error "error: FAILED(remote:unknown command)" and since I can't get into my phone, I can't use mipcsuite either or enable and settings.

Note - wipe data and format data is not the same
I've stuck with some stupid error ("erase all data" message and reboot to twrp) for hours until I formated data

jayX23 said:
I have tried going into recovery mode and wiping all data, and trying to update the firmware via the flash tool. But as I said above I can't it gives me the error "error: FAILED(remote:unknown command)" and since I can't get into my phone, I can't use mipcsuite either or enable and settings.
Click to expand...
Click to collapse
did you solve it? i also need to flash rom via mi flash tool but I do exact same error.

Pixel Experience boot loop + string of stupid decisions: is there any way out?

Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!

mkohan said:
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Click to expand...
Click to collapse
I'm new to this phone as well (but not to Android). Try the following:
Download TWRP from here -> https://androidfilehost.com/?fid=6006931924117884758
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip from here -> https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Power off phone. Hold down volume down and power button to boot into fastboot
Give the command fastboot flash recovery twrp-3.3.1-1-whyred.img to flash the recovery you downloaded earlier.
Boot into recovery
Flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip that you downloaded earlier
The above steps will at least ensure that you retain TWRP and it doesn't get overwritten by stock MIUI recovery
After that, check whether or not your phone/ROM has anti-rollback enabled and take appropriate steps accordingly.

Ok so i flashed PE 10 plus today and was met with the same problem.
Heres how i solved it
Goto fastboot option by pressing volume down and power button
Connect to pc (If it doesnt recognize, reinstall Adb drivers and phone drivers)
If it asks for decryption password just press cancel
Wipe data/internal/vendor (wont be able to wipe dalvik as it wont mount)
Flash PE 10 Plus and nothing else.
It should boot just fine.
However i run into bootloop if i flash latest magisk so i cant root my phone :/
Hope this helps

mkohan said:
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
Click to expand...
Click to collapse
hey read your post
actually adb and fastboot are two different things.
and recovery is flashed using fastboot commands not adb.
sometimes if a rom is not booting it may have issues with encryption.