hi everyone..
My wifes blade 4 (on stock firmware) crashed a few days ago, now on each boot it just goes to the stock recovery screen.
I've tried selecting the factory reset option and rebooting to no avail.
Don't know what has happened or if it's recoverable without CWM installed.
I be really grateful if anyone can help me out,
Many thanks.
ziggycat said:
hi everyone..
My wifes blade 4 (on stock firmware) crashed a few days ago, now on each boot it just goes to the stock recovery screen.
I've tried selecting the factory reset option and rebooting to no avail.
Don't know what has happened or if it's recoverable without CWM installed.
I be really grateful if anyone can help me out,
Many thanks.
Click to expand...
Click to collapse
I'm sorry to realize that this thread is mostly dead. I'm a newcomer and inexperienced with android but I seem to be the only one answering.
Here's my inexperienced thoughts: you have probably damaged the android system , a factory reset (that only wipes user related data) will not fix it.
If you had a backup with CWM ot TWRP you could probably use that to recover, but you said you don't have it, so I think you need to download the stock rom from ZTE and flash it from the stock recovery. Download the stock update.zip from ZTE and put it on the uSD, boot into recovery and update from uSD.
Use this info at your own risk
Good luck
David
Related
Hey everyone,
Have a problem with a phone that I am not able to solve for the life of me.
Model: GT-i9505
SSN: -i9505GSMH
Originally, the S4 would hang on the Samsung splash screen, since I've attempted to fix this (see below) the S4 tries to boot into recovery mode if you turn it on, but it just hangs forever. It can boot into download mode without problem, and I'm able to use Odin to write to it.
I've tried
- installing custom recoveries, both TWRP and CWM, which to my knowledge installed no problem, but it wont boot into either.
- flashing stock firmware
- flashing stock firmware & pit file
- This fix from Legija though it didn't work. And I did install the Qualcomm drivers first, which was an effort all of its own. Suggested it might be an eMMC problem, I don't know how I would be able to replace that, and instructions for bringing it back from this made little sense.
None of this has worked, and I'm not sure what I could try to get it back up and running. It doesn't matter if it's rooted, running a custom rom, or both, it just needs to work. I've Googled the **** out of this problem, no resolve, so I'd be greatly appreciative of any advice or direction anyone can provide.
Thanks,
Oz
re: stuck
ozmund said:
Hey everyone,
Have a problem with a phone that I am not able to solve for the life of me.
Model: GT-i9505
SSN: -i9505GSMH
Originally, the S4 would hang on the Samsung splash screen, since I've attempted to fix this (see below) the S4 tries to boot into recovery mode if you turn it on, but it just hangs forever. It can boot into download mode without problem, and I'm able to use Odin to write to it.
I've tried
- installing custom recoveries, both TWRP and CWM, which to my knowledge installed no problem, but it wont boot into either.
- flashing stock firmware
- flashing stock firmware & pit file
- This fix from Legija though it didn't work. And I did install the Qualcomm drivers first, which was an effort all of its own. Suggested it might be an eMMC problem, I don't know how I would be able to replace that, and instructions for bringing it back from this made little sense.
None of this has worked, and I'm not sure what I could try to get it back up and running. It doesn't matter if it's rooted, running a custom rom, or both, it just needs to work. I've Googled the **** out of this problem, no resolve, so I'd be greatly appreciative of any advice or direction anyone can provide.
Thanks,
Oz
Click to expand...
Click to collapse
I see you have done a lot of stuff but have you tried to go into recovery and do a "Factory Reset"
and restart the phone? - About 50% of the time this simple method works.
So copy a cwm/twrp flashable zip file onto your internal sdcard, do a factory reset, wipe system,
wipe cache, wipe dalvik cache then flash the zip file rom which is on your internal sdcard and see
if that does the trick.
Give it a try.
Misterjunky said:
I see you have done a lot of stuff but have you tried to go into recovery and do a "Factory Reset"
and restart the phone? - About 50% of the time this simple method works.
So copy a cwm/twrp flashable zip file onto your internal sdcard, do a factory reset, wipe system,
wipe cache, wipe dalvik cache then flash the zip file rom which is on your internal sdcard and see
if that does the trick.
Give it a try.
Click to expand...
Click to collapse
Unfortunately, I can't get into recovery, it just sits there with the blue text up the top left forever. Thoughts?
Same here
cant get into recovery either. But see the blue letters in upper left corner then reboots.... HELP
ozmund said:
Unfortunately, I can't get into recovery, it just sits there with the blue text up the top left forever. Thoughts?
Click to expand...
Click to collapse
HELP!! I have the same problem. Do you already have a solution for this?
drummerako said:
HELP!! I have the same problem. Do you already have a solution for this?
Click to expand...
Click to collapse
Nope. I took the battery out for a long time and it seemed to resolve itself, but the phone was still bust and had to be sent back.
ozmund said:
Nope. I took the battery out for a long time and it seemed to resolve itself, but the phone was still bust and had to be sent back.
Click to expand...
Click to collapse
i was in a boot loop and fix it with kies emergency firmware flash, you try that:good:
This may humor some of you as to the stupidity I have displayed in messing around with rooting\rom'ing my i9505.
Sadly tho it's resulted in me bricking/semi-bricking the phone and I am tearing my hair out trying to fix it.
What I did to get me here:
- Within TWRP (existing recovery/root at the time) I wiped all my data from the internal storage. This in effect meant that I had no roms nor any backups to recover from. Super Doh! *facepalm* moment of the centuary... :S
- For one reason or another the existing rom i was on would not boot. I was effectively stuck in a boot loop on the Samsung Logo
What I have tried doing to fix it (and failed miserably):
- I thought that by at least getting a rom onto the device and flashing it I would be back in business however this proved to be a challenge as the samsung USB drivers do not work with TWRP so I cannot adb push or sideload as I have no rom/backup locally.
- So I rooted with CWM which worked a treat with sideload. So I rom'd the phone...however...the following now happens
- I cannot get into existing/current ROM. Boot loop
- I cannot get into CWM (frozen with blue text in the top left) and have re-downloaded ODIN, CWM several times and tried to flash several times. No joy...
- I can flash with TWRP however as mentioned above the drivers do not work so I cannot sideload.
Any ideas how to fix - very very very much appreciated.
Don't need comments how dumb I have been - I am kicking myself more than you ever will.
r34l1ty7 said:
This may humor some of you as to the stupidity I have displayed in messing around with rooting\rom'ing my i9505.
Sadly tho it's resulted in me bricking/semi-bricking the phone and I am tearing my hair out trying to fix it.
What I did to get me here:
- Within TWRP (existing recovery/root at the time) I wiped all my data from the internal storage. This in effect meant that I had no roms nor any backups to recover from. Super Doh! *facepalm* moment of the centuary... :S
- For one reason or another the existing rom i was on would not boot. I was effectively stuck in a boot loop on the Samsung Logo
What I have tried doing to fix it (and failed miserably):
- I thought that by at least getting a rom onto the device and flashing it I would be back in business however this proved to be a challenge as the samsung USB drivers do not work with TWRP so I cannot adb push or sideload as I have no rom/backup locally.
- So I rooted with CWM which worked a treat with sideload. So I rom'd the phone...however...the following now happens
- I cannot get into existing/current ROM. Boot loop
- I cannot get into CWM (frozen with blue text in the top left) and have re-downloaded ODIN, CWM several times and tried to flash several times. No joy...
- I can flash with TWRP however as mentioned above the drivers do not work so I cannot sideload.
Any ideas how to fix - very very very much appreciated.
Don't need comments how dumb I have been - I am kicking myself more than you ever will.
Click to expand...
Click to collapse
Can u try flashing Stock firmware using Odin it should work and incase after flashing it does not boot go to stock recovery and wipe cache reboot
123hiten said:
Can u try flashing Stock firmware using Odin it should work and incase after flashing it does not boot go to stock recovery and wipe cache reboot
Click to expand...
Click to collapse
Just wanted to say a big thanks. Your solution worked a treat. :good:
I take it I can now root as usual? Nothing else needed? ...apart from not trying to be stupid again
Hey guys, so, i accidently took an OTA update on a rooted phone...The problem is, now the phone will only go into CWM, i've tried wiping cache, dalvik cache, factory reset, etc!! Nothing works, also even tried the "CWM Boot Loop" forum steps..Long story short, nothing works guys! When I run ADB, and i send TWRP over, my phone receives it, but then it just says "installation aborted"..SO ANY HELP IS GREATLY APPRECIATED GUYS!! Not sure if the phone is completely screwed and it's time for a new one? Or it's just an easy fix and i'm doing something wrong. Link Below from the forum i followed...
http://forum.xda-developers.com/showthread.php?t=2567493
Step 5 is where I can't get past because the phone says "Installation Aborted"^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SOLUTION:
Hey guys, fixed the phone...Basically I had to go back to bone stock..The way i did this was by going to this link BELOW
http://forum.xda-developers.com/showthread.php?t=2432476
& then I basically just downloaded what was told to be downloaded, and then followed the instructions, now what it doesn't mention is you need to flash a stock rom, apparently the software used to flash this stock rom hates all the rooted crap, like "slim rom, beanstock, cyanogen," etc...other than that, worked like a charm! took around 10-15 minutes and there it was...UP AND RUNNING .
Let me know if ya have any questions.
I recently purchased a lg g2, the korean variant f320s, it was running kitkat with a lot of bloatware on top. I successfully rooted the phone and after that i found a cwm recovery installer for this version of the phone and i hooked up the phone and ran the installer on my pc, it finished installing and the phone rebooted into the custom recovery which was in chinese i went into a menu option and then pressed the back button on the screen and the phone instantly rebooted and got stuck at lg boot logo. Is there anyway to fix this? i have tried wiping cache, dalvik and factory reset from the recovery that i can access(chinese or something) but to no avail. I can access the download mode but my pc does'nt recognize the phone and this step is crucial for i guess installing the stock rom through lg flash tools. The phone however is recognized when im in recovery and i plug it in but it only shows as a drive that is faded out and entering it shows nothing. please help me i just got it two days ago
Have you tried to use adb to sideload a rom?
playerone_ said:
Have you tried to use adb to sideload a rom?
Click to expand...
Click to collapse
i'm sorry im a complete noob in this regard could you explain a bit on how to go about doing that? i am downloading the stock kitkat rom for the model its in kdz format
.
I flashed cloudy flex rom on it through external sd in recovery and now when i boot it up it stays on lg logo for a while then screen goes black and botts up again directly into CWM recovery, please help someone...
Same problem
sheroy1995 said:
I recently purchased a lg g2, the korean variant f320s, it was running kitkat with a lot of bloatware on top. I successfully rooted the phone and after that i found a cwm recovery installer for this version of the phone and i hooked up the phone and ran the installer on my pc, it finished installing and the phone rebooted into the custom recovery which was in chinese i went into a menu option and then pressed the back button on the screen and the phone instantly rebooted and got stuck at lg boot logo. Is there anyway to fix this? i have tried wiping cache, dalvik and factory reset from the recovery that i can access(chinese or something) but to no avail. I can access the download mode but my pc does'nt recognize the phone and this step is crucial for i guess installing the stock rom through lg flash tools. The phone however is recognized when im in recovery and i plug it in but it only shows as a drive that is faded out and entering it shows nothing. please help me i just got it two days ago
Click to expand...
Click to collapse
EXACT same problem as you... Every detail is exactly the same.
I am trying to find a solution. Any luck?
.
naleyb01 said:
EXACT same problem as you... Every detail is exactly the same.
I am trying to find a solution. Any luck?
Click to expand...
Click to collapse
Yeah you just need to flash a different rom through the sd card i tried cloudy rom but it didnt work then a i tried Lamhoang rom and it did the trick im on jellybean now though and i'll try flashing something else in a month or so
ALL FIXED
You are a legend!! Device back up and running.
Okay so I installed that same rom you did but the home/back/menu buttons weren't working so not wanting to muck around, I did some quick searching (which I should have done before >.<) and worked out how to get the Cloudy roms working on a korean device.
You need "Philz cloudy f320 recovery", the kitkat baseband and the rom. LINK
1 - Install the new recovery from zip and then boot back into recovery after this. You will now be greeted with philz recovery which is awesome.
2 - From here, proceed to install the rom as noted on the rom page.
This process worked for me for the Cloudy G3 V1.3 rom.
Thanks a lot for your help!! happy to return the favour! But i am hoping the above info already does that. :victory:
naleyb01 said:
You are a legend!! Device back up and running.
Okay so I installed that same rom you did but the home/back/menu buttons weren't working so not wanting to muck around, I did some quick searching (which I should have done before >.<) and worked out how to get the Cloudy roms working on a korean device.
You need "Philz cloudy f320 recovery",
1 - Install the new recovery from zip and then boot back into recovery after this. You will now be greeted with philz recovery which is awesome.
2 - From here, proceed to install the rom as noted on the rom page.
This process worked for me for the Cloudy G3 V1.3 rom.
Thanks a lot for your help!! happy to return the favour! But i am hoping the above info already does that. :victory:
Click to expand...
Click to collapse
Good to know you got it working again i still cant figure out why this problem occurred in the first place why did the phone brick from the recovery when the recovery was working fiblne after? Also i can just get the new recovery over the one already on the phone without removing the previous one right? Thanks for the info im gonna try out the cloudy roms soon
I have no idea.. something to do with that chinese recovery I am guessing.. There are still a few issues I am going to address but for now my phone is 95% working.
The only issue is that if I try go into download mode, it still doesn't go to the second screen (All i get is the small blue dots). Bit of a pain because that's something nice to fall back on if you ever need to.
I'll search around and try and figure these out in the next week or two, but I am happy with what I have for the moment.
Yep, you literally install the new recovery over your current one and then you can restart phone back into your rom and then reboot back into recovery using an app or the button method.
naleyb01 said:
I have no idea.. something to do with that chinese recovery I am guessing.. There are still a few issues I am going to address but for now my phone is 95% working.
The only issue is that if I try go into download mode, it still doesn't go to the second screen (All i get is the small blue dots). Bit of a pain because that's something nice to fall back on if you ever need to.
I'll search around and try and figure these out in the next week or two, but I am happy with what I have for the moment.
Yep, you literally install the new recovery over your current one and then you can restart phone back into your rom and then reboot back into recovery using an app or the button method.
Click to expand...
Click to collapse
Yeah i have the same issue with the download mode as well and the phone cant seem to sync properly with the lg mobile support tool either.Do let me know if you figure something out
Hi, I'm trying to get my bricked Redmi Note 7 working again (previously flashed with a Pixel Experience ROM and after latest OTA update it's stuck at the G logo). I struggled for 2 days until my PC recognized the phone in fastboot mode and listed it correctly in Device Manager.
Today I'm finally over that step, but now i stumbled upon another issue: My phone doesn't have USB debugging enabled. I wanted to use XiaomiTool in order to unbrick it but the app asks me to enable it first.
I believe I met a dead end, no Google research helps me at all. I'm just hoping I'm this much of a newbie in the topic that I'm searching with the wrong terms or wrong places and there is indeed a solution, which is why I came here. If not, then I just got a brand new brick
I'm using OrangeFox recovery, in case that info is needed.
Yoel Bido said:
Hi, I'm trying to get my bricked Redmi Note 7 working again (previously flashed with a Pixel Experience ROM and after latest OTA update it's stuck at the G logo). I struggled for 2 days until my PC recognized the phone in fastboot mode and listed it correctly in Device Manager.
Today I'm finally over that step, but now i stumbled upon another issue: My phone doesn't have USB debugging enabled. I wanted to use XiaomiTool in order to unbrick it but the app asks me to enable it first.
I believe I met a dead end, no Google research helps me at all. I'm just hoping I'm this much of a newbie in the topic that I'm searching with the wrong terms or wrong places and there is indeed a solution, which is why I came here. If not, then I just got a brand new brick
I'm using OrangeFox recovery, in case that info is needed.
Click to expand...
Click to collapse
Hi, i had a similiar problem when two days ago i flashed the pixel experience for the first time. I wiped everything (except for the SD storage) and formatted the Data partition. That's were i made a mistake (because i should have wiped only dalvik cache, cache and data partitions, infact it worked out later with this kind of wipe.), but however i was able to fix that by flashing the boot image of the miui 11.04 from the orange fox recovery.
However, if this doesn't work, you could also try to flash the firmware of the miui 10 or miui 11 version, infact, i tried other things to fix it, and the only things which helped me to exit from the bootloop were a flash of the boot.img or a flash of the latest miui 10 global firmware (the boot image is also from the same version of the miui 10)
These things helped me to fix the bootloop on the pixel experience (or other roms like HavocOS and CRDROID). However, if you want to get back to the miui, you will have to surf the web in search of the latest rom of it and then flash it from the custom recovery by doing a complete wipe.
Unfortunately i wasn't able to put some download links because i've just registered on the XDA forum . I hope that these information will work out for you. Have a nice day .
VanGamer said:
However, if you want to get back to the miui, you will have to surf the web in search of the latest rom of it and then flash it from the custom recovery by doing a complete wipe.
Click to expand...
Click to collapse
Thanks for reply. I managed to fix it by wiping cache, dalvik and data, then formatted data partition and booted into system and my phone was fully working again.
Now i'm interested in reverting to stock MIUI to try new MIUI 11, how do i exactly do this process? Get the recovery rom in phone storage, boot into recovery, wipe necessary stuff then install the rom and that's it?
Yoel Bido said:
Thanks for reply. I managed to fix it by wiping cache, dalvik and data, then formatted data partition and booted into system and my phone was fully working again.
Now i'm interested in reverting to stock MIUI to try new MIUI 11, how do i exactly do this process? Get the recovery rom in phone storage, boot into recovery, wipe necessary stuff then install the rom and that's it?
Click to expand...
Click to collapse
Basically yes. At least that's how i did it.