Related
Hi, forum. I just switched to this phone yesterday.
I successfully rooted this phone and booted into recovery using bootstrapper.
I installed Cyannogen (the file is 808.zip) (I wiped everything before I installed.)
Now, I'm stuck with M logo screen.
When I try to recover using R+M+power button it just boots up an old recovery not clockworkmod. I don't know what to do. Please Help.
Thank you.
stuck on M
if you can when old recovery comes up hit the @ button and do a wipe that way and factory reset,.and if it wont and you start over- be sure after you load cyanogen to install clockwork and wipe 3 times just to be safe
macky722 said:
Hi, forum. I just switched to this phone yesterday.
I successfully rooted this phone and booted into recovery using bootstrapper.
I installed Cyannogen (the file is 808.zip) (I wiped everything before I installed.)
Now, I'm stuck with M logo screen.
When I try to recover using R+M+power button it just boots up an old recovery not clockworkmod. I don't know what to do. Please Help.
Thank you.
Click to expand...
Click to collapse
do the factory recovery wipe like he said make sure to just let your phone sit for a while it might take sometime to get going the first time give it up to ten minutes
if that does work the start the do a SBF again and try again
Thank you for a great support. I love you guys. though the phone is still miserably dead.
When I enter recovery it is "android system recovery" not clockwork recovery. I can do 4 things
1. reboot
2. apply sdcard: update
3. wipe data/fac
4. wipe cache
I wiped data 3 times but still no luck.
btw: if i gets cyannogen to work by miracle, would it work with Tmobile? if not I might as well give up right now!
CrackMonkey91 said:
do the factory recovery wipe like he said make sure to just let your phone sit for a while it might take sometime to get going the first time give it up to ten minutes
if that does work the start the do a SBF again and try again
Click to expand...
Click to collapse
Update : Thank you. It is now working with Cyannogen mod but I don't think it will work with Tmobile right? =[
macky722 said:
Update : Thank you. It is now working with Cyannogen mod but I don't think it will work with Tmobile right? =[
Click to expand...
Click to collapse
No. The US T-Mobile and AT&T bands are locked out on the phone. The only way to get the Pro to work on T-Moble or AT&T is to have the necessary files from Motorola, which are not publicly available. Team Black Hat has them, and they'll unlock the bands if you send them your phone and $100: http://shop.teamblackhat.info/GSM-Unlock-for-Droid-Pro-Buyer-Paid-shipping-GSM-Unlock.htm.
Im having a problem with my phone booting. it does a variety of things from rebooting mid way through boot, hanging at the white HTC screen, getting to lock screen then rebooting...
point is, i cant get in to the system.. what i'd like to do is remove everything and get it to stock... the RUU would be nice, but it needs to be booted for that to happen. i've tried a couple of custom roms (vaelpak, synergy) but they all result the same way. cleared dalvik, data, .android_secure, cache with no impact..
RA 2.3 is what the recover console currently is...
what is the best way to recover the phone to stock?
im ok with working with the phone but not awesome so somewhat detailed directions would be appreciated.
hope i didnt leave anything out,
Thanks
What rom are you on? I am assuming you can get into recovery. May I recommend, fresh 4 rom by flipz to get everything back to normal first (Full wipe is necessary) ...then we can work on this further.
thanks for the response.
wiped data/secure/cache/dalvik
applied Fresh 4.2.0.0 rom
rebooted
showed HTC white screen for 2 seconds rebooted.. did this until it gave me the 3 vibrates and flashing green light..
reseated battery and powered on
HTC white hung for what seemed longer than normal than Fresh boots.. lock screen appears for a couple of sec and then it reboots.
thanks
Lets try a few more steps before concluding hardware issues.
1. wipe all
2. http://www.virusrom.com/Tools/VR_SUPERWIPE.zip (flash this)
3. Flash your favorite rom (try one of the newer ones if your SD is partitioned)
4. restart...and let the phone wait for 10 mins...before you unlock the screen
5. unlock screen and let it settle (DO NOT SET UP ACCOUNTS)
6. reboot recovery..wipe cache and dalvik and reboot
7. sign into market...
8. if it still reboots/FCs then flash latest radios http://forum.xda-developers.com/showthread.php?t=715485
cool i'll give that a try..
when you say wipe all, is the list i've provided "all"? i noticed with RA i can wipe system/boot and some others i believe... wasnt sure i should wipe the boot or system...
yes...start at format all factory reset...and then the list you've provided...dont wipe sdcard unless formatting it...and then follow from step 2
yeah basically what i listed was the factory reset + dalvik..
so, you mention if the SD card is partitioned (app2SD?) which i dont currently have setup, but its a new SDcard so i might.. but, if i put one of those newer roms on that assume App2SD (which i believe i did) then would the problems im having be a result of doing that??
no luck, still getting random reboots
what rom did you flash? But if you did all the steps from my earlier post, I am wondering if this is an hardware issue.Heres a thread about back to stock RUU . http://forum.xda-developers.com/showpost.php?p=7529500&postcount=1
here another for the latest froyo ruu
http://forum.xda-developers.com/showthread.php?t=874251
just in case you would want to root back
well that sucks... i just replaced the screen and LCD too....
thats the tool i was trying to use but couldnt keep the system up long enough to get it to run right... in order to run the RUU you need to be in android (is that right? sounds werid, like saying in windows, past boot, etc etc).. anyways.. it has to be loaded, the RUU then flashes a special boot loader to do the restore... i've gotten a handful of errors, some of which even say that i have the wrong version (i'll try the one you posted but i've used an RUU before and tried the same one again)
i'll keep screwing with it, or get a new phone i guess.. still a year left on my contact so i'll be hitting up ebay or something :-/
thanks for all your help, really apprecaite it
Hi,
I've got a HTC Wildfire S, rooted and S-OFF.
But it's stuck in bootloop, I messed with the system/apps folder...
So now it's pretty much messed up.
Didn't install ROM-manager, I know it was kinda stupid.
How can I reïnstall a custom ROM?
Can anyone help me?
Go into recovery and flash from there, or if you backed-up then restore the rom. If you don't have any roms then you can also mount your sd card from CWM recovery. If you don't have any custom recovery then you'll have to flash it through fastboot. I would tell you the process but I'm really busy right now, but I'm sure someone will explain it to you.
Hi, thanks anyway... hopefully some other kind guy can help me
I don't have any custom recovery, only a ROM which I want to flash on to the device...
seanw712 said:
Hi,
I've got a HTC Wildfire S, rooted and S-OFF.
But it's stuck in bootloop, I messed with the system/apps folder...
So now it's pretty much messed up.
Didn't install ROM-manager, I know it was kinda stupid.
How can I reïnstall a custom ROM?
Can anyone help me?
Click to expand...
Click to collapse
Don't install custom ROM's from Rom Manager's Download list. None of them are for Wildfire S.
Install CWM Recovery either through Hboot as a PG76IMG.zip or using Eoghan2t7's Windoze tool.
From there you should make a backup of your working ROM before trying any new ones in case of times like this...
Hi,
yes if I install the CWM recovery... can I then install my ROM? It's just a slightly modified Wildfire S Stock Rom...
And, I'm sorry to ask... But how do you install CWM through the boot menu?
seanw712 said:
Hi,
yes if I install the CWM recovery... can I then install my ROM? It's just a slightly modified Wildfire S Stock Rom...
And, I'm sorry to ask... But how do you install CWM through the boot menu?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1431969
Download that and connect your WFS to your PC, follow the steps which are quite easy. Then boot into recovery (volume down + power button, choose recovery by the volume buttons and power button), then choose install zip from SD and you can install the zip file (the rom) by selecting that file.
Let me know if this works
I have the same problem when using OC ROMs.
What am I doing wrong?
Now it's loading for ages or simply stuck in the bootscreen.
I too have the same problem when using OC ROMs. Why?
Hi, thanks for the help!
But I'm not quiet through yet... so I downloaded the WFS Manager, then I connected up my phone to the pc.
It was switched on, and just doing the bootloop again, showing the "Quietly Brilliant" sign over and over again.
And then I ran the tool, and it said "Please connect up your device" after I ticked on the first option ("Root And Install Recovery").
I guess this is because the WFS was bootlooping, and so the pc didn't recognise it. I also tried with the HBOOT menu on, but still the pc didn't recognise my phone. Is there anything I did wrong?
My pc (Windows 7 Ultimate x64), showed a popup saying there couldn't be found any driver for "Android 1.0". However it did work before the bootloo
If you have a card reader, or a phone that can take your SD card, then just remove your SD card, place it in an SD card reader or a device which can take your SD card, plug that device into your PC, place the ROM you want to flash onto the SD card, place your SD card back into your Wildfire, boot into recovery and flash the ROM from there.
I had a similar situation where I had an invalid xxxxIMG.zip file on the root of my SD card and a ROM that kept rebooting my device. Naturally, I started panicking, but when I got myself together, I just realized I could remove my SD card and then go into recovery, then reinsert my card and flash a working ROM.
Hope this works for you
Hi, thanks for the help. But I don't think you fully understand my problem.
So I have a stock ROM, rooted. And I messed with the system/app folder.
Now it's stuck into bootloop.
What does recovery mean? is it the menu entry in the HBOOT menu?
Because if I go to "recovery" and click it, after a few seconds I get a phone icon with a red triangle above it.
I tried putting the PG76IMG.zip file on the root of my SD card, but then in the HBOOT Menu, I get the message:
"CID incorrect !
Update Fail!
Press <POWER> to reboot."
What do I have to do?
find the cwm recovery thread and download the PG76IMG.zip then copy it to your sdcard then reboot to hboot. when it asks you if you want to flash recovry press volume up. then when finish instead of rebooting take out your battery. wait for 25 secs reinsert it then boot to hboot then choose recovery see new ui instead of the old one.
---------- Post added at 03:19 PM ---------- Previous post was at 03:16 PM ----------
here you go forum.xda-developers.com/showthread.php?t=1213229
Hi, when I do what you say I get the error:
"CID incorrect!
Update Fail!
Press <POWER> to reboot."
This is my course of actions:
I download the PG76IMG.zip file from the CWM recovery thread.
I place it in the root of my SD-card.
I start my phone pressing the volume-down button.
It automatically finds the .zip file and tries to update, but then I get the error.
What should I do?
I got what you were trying to say, I just didn't realize you had no recovery installed. I had the same error message pop up when I tried to install the recovery. I think it had something to do with the hboot being newer than something, something, blah, blah, bliddity-blah.
Anywho, I think I had the recovery installed along with the root using SuperTool.exe, but that won't work for you, since you obviously can't boot up, so you can't connect to the PC. All I can remember is I had some sort of app on my PC that allowed me to push the CWM Recovery without going through all that hboot stuff, since the S-ON wouldn't let me install PG76IMG.zip. Again, this is useless to you
My best advice is to try another PG76IMG.zip file and just keep trying until you find one that'll work, which you'll place onto your SD card from another device, of course.
EDIT: Link to where I got CWM Recovery from.
In this post there's an auto-installer that I used to flash it onto my device.
The reason you are having bootloop problems with OC roms is because your phone doesn't support OC. Don't worry though it's not just you, even my phone doesn't support OC. The best ROM to go with right now is Alquez's CM7, but I'm sure other developers will make non-OC roms.
Hi, THANKS!
I used the auto installer, and now I have the CWM recovery!
Can someone tell me now which options I should use to install the new ROM?
Maybe an advice of which ROM would be the best one?
I'd like something fast and stable, it would be handy to have one which doesn't have any stock apps installed with it...
I'd go with Jikantaru's ROM, if I wanted a more Sense-ish experience (which I, personally, don't). It does away with the bloatware, but it keeps Sense UI. I couldn't use this one, since my SD card is only 2 gigs and I can't partition it correctly :\
Therefore, my pick would be Cyanogenmod 7, which gives you a pure Android experience (no trace of HTC's bloatware, spyware or crapware). It takes away everything you don't need or most likely don't use and keeps it all clean and speedy, since there's no Sense, MotoBlur, TouchWiz or any other company-created user interface, leaving you to run everything right on top of the Android system. However, I've had some trouble with this one. First I had no mobile data connection or WiFi, and when I finally fixed that problem, I noticed I had no phone app -.-
So, now I'm using m1ndh4x8r's ROM, and I'm pleased enough with it. It lets me overclock and stuff, though I fear I might have effed something up while reverting to it from my non-fully-working CM7 flash, and now I can't install most apps :\
Now I'm pretty much waiting for a fully-operational CM7 build to come out so I can finally use my phone's full potential.
white htc screen
Hey hey =)
I installed the cm7 by alquez (already tried the RC and the nightly build) and I'm stuck at a white boot screen - I don't know if this is the boot loop error - I only see the green HTC sign with white background
Yesterday, I unlocked the phone, rooted it and today, I installed the CWM and from there, resetted the phone, data, and installed the zip.
Now, the white screen doesnt go away, even after 15min or so
Is there a thing i'm missing?
Thanks in advance!
Saftpackl said:
Hey hey =)
I installed the cm7 by alquez (already tried the RC and the nightly build) and I'm stuck at a white boot screen - I don't know if this is the boot loop error - I only see the green HTC sign with white background
Yesterday, I unlocked the phone, rooted it and today, I installed the CWM and from there, resetted the phone, data, and installed the zip.
Now, the white screen doesnt go away, even after 15min or so
Is there a thing i'm missing?
Thanks in advance!
Click to expand...
Click to collapse
Wipe all data and cache including dalvik from within clockwork mod
ok, shall I also format boot?
because I read it's pretty nasty deleting it if you don't install a new one, is that right? ^^
Dunno what has changed but thank you for your tip, it worked now!! =)
PS: didnt format boot ;-)
Hey, everyone!
So within the past week or two my stock standard HTC One X started playing up, which I'm pretty sure was a result of a recent system update (to 4.2.2, from memory). My 'twilight' app (similar to f.lux but for phones) started randomly turning on and off for no reason, the screen became very rapidly unresponsive unless a great deal of force was applied or the phone was repeatedly locked and unlocked, it began to heat up (even more so than normal), etc, etc. Yesterday the unthinkable happened: it got stuck in a bootloop.
So here's how I wound up where I am right now.
I came to terms with the fact that I was going to lose all of my data (at least Google has automatically backed up my images and videos every few days), and anyone important enough to me that I need their phone number I also have on facebook/google plus or see frequently enough in person that when the issue is resolved I can add their numbers again. So I performed a factory reset hoping that would fix the problem. It didn't. Today, at the behest of a friend of mine, I decided to flash a custom ROM on my phone in an effort to salvage what was increasingly likely looking to be a $600 paperweight. I've never done this before, so I followed the instructions in the following video exactly as shown, and downloaded the latest stable version of Cyanogen mod for the One X. The video can be found by googling, "HTC One X - How To Root (in-depth)". It's the first result.
Everything went... well, not smoothly. But I got there in the end. Eventually the phone rebooted, and the blue (or cyan, I suppose) Cyanogen mod logo came up with the circular loading symbol tracing around it. It stayed this way for some 30 minutes or so. I decided to reboot the phone. Same issue again. I performed a factory reset, cleared the cache, cleared the Dalvik cache, and rebooted again. Still wouldn't pass the booting process. I cleared everything a second time and even reinstalled the update.zip (which for some reason appeared as update.zip.zip in ClockworkMod Recovery v5.8.2.7... I'm wondering if that caused some issue). Still no progress. Eventually, out of frustration, I began playing around with random settings within Clockwork Mod Recovery and tried backtracking a few steps computer-side in terms of the installation process, and somewhere along the way I've really F'd things up.
And here's the current situation.
Now, whenever the phone restarts the white HTC splash comes up, followed very quickly by a black screen which flickers momentarily, and then immediately jumps to ClockworkMod Recovery (v5.8.2.7).
Whereas earlier today both fastboot and adb recognised my device, now only fastboot will. I can't get anything to appear in the adb device list anymore. I'd prefer it if people didn't immediately scream, "DRIVER ISSUE!" considering adb worked for half of the day so it seems relatively unlikely to me that that's the problem.
My computer itself won't recognise that my phone is plugged in (probably because there's no OS anymore by the seems of things). I've tried two USB cables to no avail (the first worked earlier on this afternoon, so that shouldn't be an issue).
Within the 'choose zip from sdcard' section of ClockworkMod Recovery I can choose from (other than all of the files that were already in there):
CWN-SuperSU-v0.87.zip
update.zip.zip (the double file extension really bugs me)
'mount USB storage' within ClockworkMod Recovery gives me an erroy reading, E: Unable to open ums lunfile (No such file or di...) (runs off the screen, although presumably it just says no such file or directory exists).
I can't think of anything else that's relevant or would help troubleshoot this issue. If you need anymore info please just let me know and I'll do my best to supply it (you may have to lead me through the data acquisition process, however). I'm really hoping the phone isn't completely bricked because I don't exactly have the money right now to buy a new phone - I'm a uni student who only works part time and I just bought a car a few weeks ago. Bye bye, savings.
Regards,
Scott.
man, stupid question, did you flash the boot.img in the bootloader before or after flashing the rom?
if yes,
what cyanogen did you install?
cyanogen 10.2 should work with your recovery but cyanogen 11 needs a particular one
edit:did you make a backup (in the recovery) before flashing?
Want a working phone for now, follow this :
Download this recovery and flash it :
https://www.dropbox.com/s/qp21ubo10xetcvn/Philz recovery 5.15.9.img
Download a sense 5 rom like arhd or blade from the forum here. Copy the boot.img from the rom and flash that too. Then enter the recovery and mount the sdcard as a usb mass storage device and wait as long as it needs to pop up on the pc.
Copy the rom to the sdcard and then perform a full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache, data and system
Then install the rom.zip and reboot.
Husky34 said:
man, stupid question, did you flash the boot.img in the bootloader before or after flashing the rom?
if yes,
what cyanogen did you install?
cyanogen 10.2 should work with your recovery but cyanogen 11 needs a particular one
edit:did you make a backup (in the recovery) before flashing?
Click to expand...
Click to collapse
I flashed SOME .img file, but not one called 'boot.img'. Can't remember when, unfortunately. If you find the youtube video I mentioned I followed that exactly.
No recovery unfortunately. I saw no point given that the phone was almost unusable in any form prior to me getting Cyanogen installed (it was constantly and randomly rebooting). Probably a mistake in retrospect.
Version 10.2, by the way.
Mr Hofs said:
Want a working phone for now, follow this :
Download this recovery and flash it :
Download a sense 5 rom like arhd or blade from the forum here. Copy the boot.img from the rom and flash that too. Then enter the recovery and mount the sdcard as a usb mass storage device and wait as long as it needs to pop up on the pc.
Copy the rom to the sdcard and then perform a full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache, data and system
Then install the rom.zip and reboot.
Click to expand...
Click to collapse
Can you walk me through it step-by-step. Again, I'm a total noob to this and I DON'T want to stuff this up again. Is the fact that adb (or my PC in general) isn't recognising my phone going to make this difficult? I mean how am I meant to copy anything to the SD card if I can't access it through windows explorer or via adb push?!
You need fastboot. Rename my linked recovery to just recovery.img and flash it :
Fastboot flash recovery recovery.img
Fastboot erase cache
Flash the boot.img from the rom :
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and follow earlier given steps
Mr Hofs said:
You need fastboot. Rename my linked recovery to just recovery.img and flash it :
Fastboot flash recovery recovery.img
Fastboot erase cache
Flash the boot.img from the rom :
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and follow earlier given steps
Click to expand...
Click to collapse
This seems to work at first - instead of jumping into ClockworkMod Recovery, after flashing the image file you gave me, it jumps into a new recovery mode. But after rebooting and going into recovery mode again it's back to ClockworkMod Recovery (I made sure to clear the cache).
You mean the old cwm. The new one is cwm based and looks just like it. If it's flashed it can't be gone without flashing something else as a recovery !
Mr Hofs said:
You mean the old cwm. The new one is cwm based and looks just like it. If it's flashed it can't be gone without flashing something else as a recovery !
Click to expand...
Click to collapse
Oh. Well it looks different the first time I boot into recovery versus the second time (PhilZ Touch 5 with a distinct purple background the first time, but the second time it goes back to a black background with blue text).
Not really sure how to proceed from here. Battery is dropping fast (9%) despite being plugged in, so I'm worried if I don't fix this ASAP it'll be forever FUBAR.
The old one does not support charging. Try flashing philz again and keep it in there and charge it up as Philz does enable charging in recovery.
If you use Fastboot flash recovery command the old one is gone.....can't come back like that !
Mr Hofs said:
The old one does not support charging. Try flashing philz again and keep it in there and charge it up as Philz does enable charging in recovery.
Click to expand...
Click to collapse
Mr Hofs, you sir are a gentlemen and a scholar! I have managed to get back to the initial bootscreen for Cyanogen mod. AND SUCCESS! IT JUST PASSED THAT SCREEN AS I WAS TYPING!
I am indebted to you, you glorious man! Thank you so very much I'll keep you guys posted (for better or worse)!
Hope it will be fine. I will keep an eye out here
Mr Hofs said:
Hope it will be fine. I will keep an eye out here
Click to expand...
Click to collapse
So I tried updating the camera (?) as a suggested update after getting back into my phone, and it's already stuffed up again. It rebooted and said that root access has possibly been lost. What's happening now?
Doesn't appear to be a big issue for now, actually. Reset, not caused any problems since then! Managed to get google apps working, and downloaded a bunch of the apps I need All's well!
Thanks one again!
Alright ! Hope i don't see you here again
Hi all - I have been searching these threads for hours and hope I can bother for some assistance. I too have soft bricked, I went to install Android Revolution HD 33.1 but missed a step. I am currently Tampered, unlocked, and S-On. I have TWRP v2.5.0.0. When I mount the sd card in TWRP, and try to copy files over, I get a message from the PC to format the sd card - I didn't for fear of wiping out everything and hardbricking the phone. I am a noob when it comes to using commands/fastboot to copy files over. I am sorry to ask, but can someone please help me with exactly what to type?
Oh - and do I need to use philz recovery since I have TRWP installed and can access?
darule_2011 said:
Hi all - I have been searching these threads for hours and hope I can bother for some assistance. I too have soft bricked, I went to install Android Revolution HD 33.1 but missed a step. I am currently Tampered, unlocked, and S-On. I have TWRP v2.5.0.0. When I mount the sd card in TWRP, and try to copy files over, I get a message from the PC to format the sd card - I didn't for fear of wiping out everything and hardbricking the phone. I am a noob when it comes to using commands/fastboot to copy files over. I am sorry to ask, but can someone please help me with exactly what to type?
Oh - and do I need to use philz recovery since I have TRWP installed and can access?
Click to expand...
Click to collapse
TAMPERED ? what does your hboot say :
1: ENDEAVORU
2: EVITA
Mr Hofs said:
TAMPERED ? what does your hboot say :
1: ENDEAVORU
2: EVITA
Click to expand...
Click to collapse
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
Radio-0-19as.32.09.11_2
As i thought. You are in the very wrong forum. Head over to the HTC ONE XL forum....AT&T .....
Mr Hofs said:
As i thought. You are in the very wrong forum. Head over to the HTC ONE XL forum....AT&T .....
Click to expand...
Click to collapse
uh oh, that doesn't sound good for me...I don't have the XL version, just the one X. Will that matter? Did I flash this baby using files for the XL when I should have used something else?
No you don't read well. You have the HTC one XL (EVITA) and this forum is for the ENDEAVORU HTC one X international version.
We here have the quad core and you there have the dual core phone !
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.