[Problem Solved]
Method is in my next post.
-------
Dear Friends!
Salaam!
I decided to updated my ROM to JB4.2. In order to do this, I formatted my memory card (which deleted all data including old backup) and made fresh backup using Clockword Recovery.
After that when I started the cell, it was on loop. LG logo appears and after that boot-screen logo appear and after that cell phone restarts.
I installed few roms, and same thing is happening again and again. Phone starts, LG logos appears, Rom boot screen appears and sometime language selection shows and phone starts again. This is happening again and again.
- I tried to restore my backup but no sucess.
- I have wiped every thing (Factory reset, Cache, Dalvik and even Batt Status).
- I'm using latest official recovery CWR.
- I tried, Avatar, Pac Rom, CM10, ICS and other too. But no success.
Kindly guide. Highly appreciated.
Looking forward.
---
Dr Faryal Saeed Abdal
I am having the EXACT same issue!
faryal said:
Dear Friends!
Salaam!
I decided to updated my ROM to JB4.2. In order to do this, I formatted my memory card (which deleted all data including old backup) and made fresh backup using Clockword Recovery.
After that when I started the cell, it was on loop. LG logo appears and after that boot-screen logo appear and after that cell phone restarts.
I installed few roms, and same thing is happening again and again. Phone starts, LG logos appears, Rom boot screen appears and sometime language selection shows and phone starts again. This is happening again and again.
- I tried to restore my backup but no sucess.
- I have wiped every thing (Factory reset, Cache, Dalvik and even Batt Status).
- I'm using latest official recovery CWR.
- I tried, Avatar, Pac Rom, CM10, ICS and other too. But no success.
Kindly guide. Highly appreciated.
Looking forward.
---
Dr Faryal Saeed Abdal
Click to expand...
Click to collapse
it appears you have solved your problem ... if that is correct , can you post how did you solve it ? for other people assistance
thanks
Thanks to the XDA, slimbaba (Mohammad Ali) and expression104 and devcon69 from TipidCP.com
Mohammad Ali was a big help.
Problem was with my USB drivers which I couldn't flash phone properly.
The most useful links for flashing are
http://www.tipidcp.com/viewtopic.php?tid=33686&page=1
http://wiredsoup.blogspot.com/2013/02/lg-optimus-su640-comfirmed-working.html
I'll be happy to help, if any one needed.
Related
Hi guys, i wish you a happy new year...
My phone turns normally but after logo of Lg, after of the boot
And don't show the logo of android, but play sound of the start (sound in the spacework of android or launcher)
but don't show nothing in the screen, but the screen is good, but show recovery, etc...
i do a full hard reset and nothing
i flash with kdz and nothing
with beta 9 of cyanogen mod 9 start the phone but, this rom has very errors, but other custom or original rom don't turns to 100% the phone,
plase help me, how can i for own the original firmware....
thanks
nykholay said:
Hi guys, i wish you a happy new year...
My phone turns normally but after logo of Lg, after of the boot
And don't show the logo of android, but play sound of the start (sound in the spacework of android or launcher)
but don't show nothing in the screen, but the screen is good, but show recovery, etc...
i do a full hard reset and nothing
i flash with kdz and nothing
with beta 9 of cyanogen mod 9 start the phone but, this rom has very errors, but other custom or original rom don't turns to 100% the phone,
plase help me, how can i for own the original firmware....
thanks
Click to expand...
Click to collapse
What recovery are you using? What ROMs have you tried flashing? Have you wiped every partition, including system, data, and cache?
resp
osamabinary said:
What recovery are you using? What ROMs have you tried flashing? Have you wiped every partition, including system, data, and cache?
Click to expand...
Click to collapse
Recovery: AmmonRa.
Roms:
ICS beta : result: turn on phone [posible fix] but has errors
ICS RC: result: don't turn on phone.
ICS xperia: result don't boot phone
Original Firmware: Lg p350: fail, don't can be turn on screen. Lgp350g firmware: =
The exact Model is: LG-P350G
Wit Kernel by Kamesh turn on screen but phone don't quest normally, unestable.
Wipe: all partitions
Rom: Flash with any version
recovery: AmmonRa
Fash with fastboot
Maybe your Recovery is broken. Next time flash ClockworkMod (PecanCM version) and give full wipe (minus SD-Card). After download Flashable Firmware (search a little bit on our Android Development and you find it, was made by Skyheiser) and flash it and see if the problems still exist.
Hi,
Recently my brother gave up on his G-Nexus due to some complications that I soon discover. After he gave up reviving his phone, I took the liberty to try to ''revive'' his phone and found the same frustration that plague my brother.
Here's the thing:
1. I reflashed STOCK ROM + UNROOT. (tried 4.0.4/ 4.2.2/ 4.3. No success)
2. the phone is unable to BOOT, just BOOT LOOPs.
3. CAN boot into FASTBOOT.
4. unable to enter STOCK RECOVERY. (or in any rare case I could, cleared data, but bootloop persists).
5. fastboot flashed recovery TWRP and CWM , cleared data, reboot, and bootloop persist.
I'm out of option. I've googled for hours and nothing seems to help. Hoping the members here could provide assistance.
I've sent the phone for a troubleshoot, and the man told me it was the motherboard that was the case.
The thing with this is that I've flashed different stock ROMS and wasn't able to boot, not one successful boot.
My theory is that I've had a corrupted NAND?
Could anyone help me?
Thanks in advance.
blooddoom said:
Hi,
Recently my brother gave up on his G-Nexus due to some complications that I soon discover. After he gave up reviving his phone, I took the liberty to try to ''revive'' his phone and found the same frustration that plague my brother.
Here's the thing:
1. I reflashed STOCK ROM + UNROOT. (tried 4.0.4/ 4.2.2/ 4.3. No success)
2. the phone is unable to BOOT, just BOOT LOOPs.
3. CAN boot into FASTBOOT.
4. unable to enter STOCK RECOVERY. (or in any rare case I could, cleared data, but bootloop persists).
5. fastboot flashed recovery TWRP and CWM , cleared data, reboot, and bootloop persist.
I'm out of option. I've googled for hours and nothing seems to help. Hoping the members here could provide assistance.
I've sent the phone for a troubleshoot, and the man told me it was the motherboard that was the case.
The thing with this is that I've flashed different stock ROMS and wasn't able to boot, not one successful boot.
My theory is that I've had a corrupted NAND?
Could anyone help me?
Thanks in advance.
Click to expand...
Click to collapse
If you've flashed the phone back to stock and it still won't boot then there's probably nothing you can do. Time for a new phone.
Hi guys,
I briefly describe the situation: I've got a "working" system ROM (CM11) which is rebooting after about 30 seconds from home screen boot; I decided to do a full wipe, just to make the thing faster; now the problem, when I try to wipe everything TWRP says everything is done well, but nothing changes, it means I've got the same old stuff on my phone. What can I do? Thanks in advance.
PS. I also tried to go back to stock with factory image of Android 4.3, but it get stuck on writing 'system'. It seems everything is read only!
INFO: TWRP 2.6.3.2, CM 11 M12
Emmc fried.
Hi,
I flashed on my SM-T805 with wifi and LTE the new Ironrom 2.5 . On my first try something was damaged, dont know why and what. Then via Downloadmode TWPR 2.5 with autoroot. Now I wiped everything in TWRP and after that I wiped the System via advanced...
Of course I have a backup, done with TWRP 3. I restored it but it also didnt worked. After a reboot I just get the Samsung Logo with the flying Pixels. Maybe a Bootloop?
After that the wiping Session again, flashing Samsung Firmware, flashing Iron Rom 2.5.
Now I waited endless just with the Logo and after that - maybe 20 Min or longer - was the first start of Iron Rom. After a new reboot again: Just the Samsung Logo till the akku was empty....
a.) How I'm able to format delete ALL? Or what should I do?
b.) could it be that the Backup didnt restored correctly cause it was made with TWRP 3 and restored with TWRP 2.x? Dont think so...
But who knows...
c.) does anyone know a functional Cyanogen for the SM-T805?
Please give me links too (ROMs, Tools, etc) in case of an answer.
Thank you in advance, good times and peace
Follyx
Hi people,
Today I unlocked my Lenovo ZUK Z2 Plus and installed latest twrp recovery 3.3.1 successfully(no errors until now, butter smooth). After that I flashed "CARBON-CR-7.0-OPAL-RELEASE-z2_plus-20200122-0608" without installing GApps. This time the ROM booted successfully. I was able to use the phone and make calls.
Then I installed the GApps " open_gapps-arm64-9.0-stock-20200131.zip" downloaded from OpenGApps.org. This time around, when I booted after installing GApps, the phone showed the welcome screen, but got suddenly turned off. After that the phone just shows ZUK logo and keeps rebooting.
To fix this, I went to recovery again, wiped clean DATA & DALVIK CACHE & CACHE & SYSTEM & VENDOR partitions, hoping I would start from the beginning and again install only ROM and not GApps and hoping I would be able to use the phone.
Now this time around, even though I wiped every partition that TWRP shows, the phone just kept rebooting without starting Android OS. So I cleaned again everything using TWRP(cleaning DATA procedure) and then transferred ROM zip files to phone and again flashed only ROM. Still the phone kept rebooting.
Now I got pissed off. I flashed factory ROM using QFIL method. This time after the boot animation it went straight to "Shutting Down" dialogue and again the phone restarted.
CAN SOMEBODY TELL ME WHAT THE HELL IS EXACTLY WRONG WITH MY PHONE?
WHAT COULD HAVE GONE WRONG THAT EVEN AFTER CLEANING ALL THE PARTITIONS AND FLASHING USING THE FACTORY PROCEDURE, THE PHONE STILL KEEPS REBOOTING?
Is there any other partition that needs to be cleared(which the TWRP does not list)?
Can somebody just tell me how to get out of this?
(Please explain the steps and the reason for each, as I am a noob in this matter).
WAITING FOR ANYBODY'S PROMPT RESPONSE AS MY PHONE IS COMPLETELY UNUSABLE. THANKS IN ADVANCE.
what ZUI version you flashed with QFIL ?
AndroidUser5 said:
Hi people,
Today I unlocked my Lenovo ZUK Z2 Plus and installed latest twrp recovery 3.3.1 successfully(no errors until now, butter smooth). After that I flashed "CARBON-CR-7.0-OPAL-RELEASE-z2_plus-20200122-0608" without installing GApps. This time the ROM booted successfully. I was able to use the phone and make calls.
Then I installed the GApps " open_gapps-arm64-9.0-stock-20200131.zip" downloaded from OpenGApps.org. This time around, when I booted after installing GApps, the phone showed the welcome screen, but got suddenly turned off. After that the phone just shows ZUK logo and keeps rebooting.
To fix this, I went to recovery again, wiped clean DATA & DALVIK CACHE & CACHE & SYSTEM & VENDOR partitions, hoping I would start from the beginning and again install only ROM and not GApps and hoping I would be able to use the phone.
Now this time around, even though I wiped every partition that TWRP shows, the phone just kept rebooting without starting Android OS. So I cleaned again everything using TWRP(cleaning DATA procedure) and then transferred ROM zip files to phone and again flashed only ROM. Still the phone kept rebooting.
Now I got pissed off. I flashed factory ROM using QFIL method. This time after the boot animation it went straight to "Shutting Down" dialogue and again the phone restarted.
CAN SOMEBODY TELL ME WHAT THE HELL IS EXACTLY WRONG WITH MY PHONE?
WHAT COULD HAVE GONE WRONG THAT EVEN AFTER CLEANING ALL THE PARTITIONS AND FLASHING USING THE FACTORY PROCEDURE, THE PHONE STILL KEEPS REBOOTING?
Is there any other partition that needs to be cleared(which the TWRP does not list)?
Can somebody just tell me how to get out of this?
(Please explain the steps and the reason for each, as I am a noob in this matter).
WAITING FOR ANYBODY'S PROMPT RESPONSE AS MY PHONE IS COMPLETELY UNUSABLE. THANKS IN ADVANCE.
Click to expand...
Click to collapse
Greetings buddy,
For my interest, i would like to know that the carbon rom u flashed was based on Android 9 or Android 10????
arielcasari said:
what ZUI version you flashed with QFIL ?
Click to expand...
Click to collapse
zui 2.5 st which is meant for indian users.
Naresh Rawat said:
Greetings buddy,
For my interest, i would like to know that the carbon rom u flashed was based on Android 9 or Android 10????
Click to expand...
Click to collapse
android 9.0.
what could be the problem... what do you think?
AndroidUser5 said:
android 9.0.
what could be the problem... what do you think?
Click to expand...
Click to collapse
I m at job so i reply late. No offense please ???
Ok plz let me know that if ur device boots up to fastboot mode. If yes then repeat the whole process but this time try installing different twrp. U can also use (https://www.androidfilehost.com/?a=show&w=files&flid=38683) tool kit for flashing. (DO NOT TRY TO RELOCK BOOTLOADER USING THIS TOOL) Also use flame gapps.
Will catch u soon regarding ur issue.
Peace out n TY???
Naresh Rawat said:
I m at job so i reply late. No offense please
Ok plz let me know that if ur device boots up to fastboot mode. If yes then repeat the whole process but this time try installing different twrp. U can also use (https://www.androidfilehost.com/?a=show&w=files&flid=38683) tool kit for flashing. (DO NOT TRY TO RELOCK BOOTLOADER USING THIS TOOL) Also use flame gapps.
Will catch u soon regarding ur issue.
Peace out n TY
Click to expand...
Click to collapse
i have already tried using twrp 3.2, but no luck. I will try flame gapps and will let you know. i will try this coming saturday.
Dhanyavad.
Naresh Rawat said:
I m at job so i reply late. No offense please
Ok plz let me know that if ur device boots up to fastboot mode. If yes then repeat the whole process but this time try installing different twrp. U can also use (https://www.androidfilehost.com/?a=show&w=files&flid=38683) tool kit for flashing. (DO NOT TRY TO RELOCK BOOTLOADER USING THIS TOOL) Also use flame gapps.
Will catch u soon regarding ur issue.
Peace out n TY
Click to expand...
Click to collapse
I again flashed the Stock ZUI 2.5. ST ROM using QFIL. But before doing this I had moved the SIM Card to another fone, so this fone was without any connection. This time the fone booted up successfully. Then I reflashed the Carbon ROM mentioned before and flashed Flame GApps Basic edition as suggested by you. This time the fone booted up successfully. But as soon as I connected the fone to internet, it downloaded something from Google Play Services in the background and again it started the same problem.
SO BASICALLY WHEN IT DOWNLOADS SOMETHING FROM GOOGLE IN BACKGROUND, IT STARTS THE REBOOTING NONSENSE.
I searched the internet for this and some articles on the internet suggested that "Google Dialer" component is causing reboot. Those articles suggested that if the "Google Dialer" is not set as the default dialer, it reboots. BUT HOW TO SET IT AS DEFAULT, WHEN IT STARTS REBOOTING IMMEDIATELY AND IT DOES NOT GIVE ENOUGH TIME?
EVEN THE EARLIER GApps 9.0 stock package that I flashed had warned to set the "Google Dialer" as default, but upon boot up it kept rebooting.
Even initially I started this UNLOCKING AND CUSTOM ROM FLASHING exercise after the factory ROM started rebooting after updating "Google play services".
So this seems to me an issue from Google.
Has Google done this on purpose to make people switch older phones to new ones?(Because I own a total of 3 android devices and only this device is rebooting not the other ones).
Looking forward to your reply.
Greetings Buddy..how's life going??
Ok once again I hv read ur op regarding ur problems. Let's start from the beginning. Boot up to twrp and format the data first before wiping everything. Try flashing lineageOS 16 using official gapps. (Flash gapps along with the flashing ROM, same time. Because flashing gapps after ROM's 1st reboot may result synchronise error or sometime bootloop). If successful, then flash ur carbon ROM and see whether it boots up to normal or still gives such error.
BTW sorry for my late replies. Till then peace out
Naresh Rawat said:
Greetings Buddy..how's life going??
Ok once again I hv read ur op regarding ur problems. Let's start from the beginning. Boot up to twrp and format the data first before wiping everything. Try flashing lineageOS 16 using official gapps. (Flash gapps along with the flashing ROM, same time. Because flashing gapps after ROM's 1st reboot may result synchronise error or sometime bootloop). If successful, then flash ur carbon ROM and see whether it boots up to normal or still gives such error.
BTW sorry for my late replies. Till then peace out
Click to expand...
Click to collapse
I am now not able to boot any ROM. Just keeps rebooting after the ZUK splashscreen. Hence, I again reflashed the Recovery properly, using the procedure as before. Now I am not able to boot into the recivery, too.