Blu Life Pure XL 16gb Ver. Soft Brick(?)
so i tried flashing the indian stock room (16gb) via GNQC and in the end it keeps boot looping. I've read that there is a problem with the NON-HLOS (modem) and that's why the conflict appears. Any idea about how fix this problem? I can enter stock recovery (can't see inside of sdcard) and fastboot.
Wrong forum. This is the Blu Pure XL which comes out later this month.
Related
Hey folks,
i got a serious issue with my MotoG...
I tried to install/flash the GPe Rom (Android 4.4.2) here from xda and it fully worked. After the install process i received the OTA Update to Android 4.4.4 and installed it with the stock recovery. The result was a working up to date GPe rom where i deleted some system apps. I rebooted the phone and got stuck at the boot logo from Google with the unlocked symbol. A full wipe and reflash of the GPe Rom didn't fixed the problem. The phone sticks at the boot logo. After this i tried to reflash the Motorola Rom which didnt fixed it either....
My guess is that the OTA Update from GPe changed something which can't be fixed with older firmware flashes...!?
After a couple of hours of work i pushed via adb my CWM backup to the internal storage and restored it. My Moto booted and i was finally able to get it back to run the stockrom.
Then i saw something weird... The google logo with the unlock symbol stays and then the motorola boot logo appears and im not able to flash via fastboot other rom
Anyone experience similar or the same problem after restore from GPe 4.4.4 to lower Android version 4.4.2?
Thanks in advance for help and tipps
Flamey
many peopla have bricked phones right now
we have to wait for fastboot images of 444 or gpe 444
there are none yet
Yeah I'm luckily half bricked..
Can't flash stock..
Stuck with CM based ROMs..
I go either side and my phone dies..
Sent from my Moto G using XDA Premium 4 mobile app
http://forum.xda-developers.com/moto-g/general/howto-fix-stuck-boot-downgrading-t2808098
you can use that
lol sorry, you fixed the issue by your own guide, lol
HI
I tried to flash a no stock kernel and my moto g was in bootloop
then I tried to do all reset and in the TWRP I did a system reset
I tried to remedy ah i flashed a software stock with fastboot method following the guidance in the forum but the first steps give me the result of " failed"
after using the guide the motion g is still in bootloop
I do not know how to unlock it
Any advice?:crying::crying:
Valeri0 said:
HI
I tried to flash a no stock kernel and my moto g was in bootloop
then I tried to do all reset and in the TWRP I did a system reset
I tried to remedy ah i flashed a software stock with fastboot method following the guidance in the forum but the first steps give me the result of " failed"
after using the guide the motion g is still in bootloop
I do not know how to unlock it
Any advice?:crying::crying:
Click to expand...
Click to collapse
While posting such thing you should provide much more & clear information for the people who would like to help you
1 what is ur device (32,33,GPE)
2 what was the base ROM
3 what kernel you flashed
I assume you are on stock ROM and flashed aosp kernel
Just flash any stock based kernel... Like faux or Aero kernel(search in development sections) your phone should be up and running
Please only post development threads in the development section
Questions belong in the Q&A section
Thread moved
You need to flash the 4.4.4 O2 UK firmware image available here:
http://forum.xda-developers.com/showpost.php?p=54872143&postcount=362
Alternatively flash the XT1032 Retail EU ROM available here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
-i have a moto g x1032 with gpe software
-the stock GPE
-I I tried to flesh the aereo kernel
I wanted to flash another stock kernel but the problem is that: on the memory of the moto g I have no other kernel and not being able to turn I can not put new kernel in the memory
Power on holding 'vol' down. You can flash the original GPe boot.img (kernel) via this fastboot screen:
mfastboot flash boot boot.img
FYI, from your screenshot you are attempting to flash the O2 UK 4.4.2 firmware image.
in the guide on xda was written that I could fleshare another software and I chose one at random because i could not find the italian software...what can i do ?
I lost the phone forever or can i unlock it?
Hi everyone, I have a HTC Desire 820s running Kitkat 4.4.4 but there is a Taiwanese variant, the Desire 820ys which runs on Lollipop 5.0.2 and Sense 7 out of the box. Both are MT6752 MTK devices code named htc_a50ml_dtul.
I was able to get RUU zip for the Lollipop variant and thanks to nkk71 it was successfully decrypted without any errors. So I created a zip file using the boot.img and system.img and was able to successfully flash it with TWRP. The problem is that after flashing, the phone cannot boot into the system or recovery, HTC logo appears for about 30 secs, then it switches off for about 5 secs and the cycle continues(bootloop?). I could easily fix this with flashing kitkat boot.img with SP Flash Tool (cannot flash anything with the bootloaders in both phones )
What could be preventing the ROM from booting considering that they are of the same model hence no porting is required?
The boot file I extracted from the decrypted RUU was named boot_verified.img, does this mean it is signed or looks for some signatures before booting into recovery or system?
Thanks in advance
Up
Hi,
As you should know, you may try to ask in your own dedicated forum to get better help:
Desire 820 Q&A, Help & Troubleshooting
Good luck.
I tried a cm12.1 rom which used to get flashed perfectly without any issues earlier. Then i encountered some problems with the ROM and i decided to flash the stock international kitkat rom(yes, i followed the correct procedure from the guide by @codelover). I didn't unlock the bootloader nor root it nor flashed a custom recovery.
For the past few day's i've been trying to install the same cm 12.1 rom and some new cm12.1 roms(updated versions, here is the link:https://userscloud.com/go/kgu385awbw9z/) but without any luck. After flashing either of the roms, the phone boots up fine till the stage where it shows the static honor logo(non-animated one) but after that it just shows a black screen and just stays there.
If i reflash stock B115, B108-signed 4.2.2 roms and B320 kitkat rom, it happens perfectly. But if i flash any other roms (after unlocking the bootloader and flashing custom recovery by following the guide), the black screen problem pops up(which didn't used to happen earlier). AGAIN i have tried the older cm12.1 ROM whose zip file has been stored on the sd card since that day without any modifications, so there's no chance of the ROM being tampered with.
I have tried hard resetting it by deleting emmc partitions and then reflashing the stock roms, but still the problem pertains after flashing the custom roms.
Does anyone know where i might be going wrong or what the problem is?
Hi guys,
Not sure if anyone else has had this issue, but I've only got a Moto G 4G fairly recently (my Nexus 5 died) and have been attempting ROM flashing (never had an issue with multiple Nexus phones & tablets) I was flashing the rom OK but the sim card wasn't recognised - so went back to rooted stock Kitkat & Xposed.
Today I thought I'd give it another go, got into TWRP, advanced wipe as usual...but it didn't complete and the phone suddenly booted back into the system (with the Android upgrading/optimizing message you usually get when starting a new phone)
System is untouched, still rooted/xposed etc. Does anyone have an idea why this has suddenly happened? Never encountered anything like this before. TWRP is the latest version 3.1.1.0
Any suggestions welcome, cheers.
Just thinking....would flashing with adb be a solution?
Just flash lollipop stock ROM using mfastboot
later you can flash twrp recovery and then proceed with the nougat or oreo based ROM.. Bootloader should be updated so my suggestion is flash lollipop stock ROM