Hi, All
I've been flashing for some time now. but i got a blaze 4g from a friend which was working perfectly till i tried to flash a custom ROM. i got a status 7 error, and the phone hasn't been alright since then. i flash via twrp, but it gets stuck at every boot up (i.e. gets stuck after bootanimation, and "preparing SD card). I restored the backup of the stock rom (gb). but it just also gets stuck at after booting up, the same way! audio not working too. i dont know what i'm doing wrong. ever since, every ROM i flash, does same. please help. i've tried everything i know: odin to stock, flash kernels, and all. any help would be highly appreciated. cm10 was responding well, but anything to do with audio just makes the phone freeze and reboot. i cant make calls, nor receive any' but network signal is there. please help
Have you factory reset after each flash?
from the depths of Sawny TL
yes, i have. even formatted system and all... but still persists.
i just wish @k0nane gets to help me out.
Usually a status 7 means recovery is incorrect for the rom you're flashing. Which twrp are you using?
Sent from my VS980 4G using XDA Premium 4 mobile app
Why not Odin back to stock and redownload all the materials.
You must've installed a bad zip. (Bad download)
Sent from my SAMSUNG-SGH-T769 using Tapatalk
thanks guys, but i've tried all your suggestions already, but none worked.... but i updated the cwm recovery to 6.0.3.8 and updated the radio to UVMB1... Now everything is fine. once again, thanks to yall for your help. really appreciated.
Related
Good day all, I recently got a Nexus S for free from my brother becuase it keep's restarting its self. The phone was rooted with Cyanogen rom, and from what he told me has been dropped a couple of times. With this all being said, he went ahead and flashed a fresh rom on there (unk which one) and wiped everything etc.. Anyone exp this type of problem before and if so what can be done to fix it?
King350z said:
Good day all, I recently got a Nexus S for free from my brother becuase it keep's restarting its self. The phone was rooted with Cyanogen rom, and from what he told me has been dropped a couple of times. With this all being said, he went ahead and flashed a fresh rom on there (unk which one) and wiped everything etc.. Anyone exp this type of problem before and if so what can be done to fix it?
Click to expand...
Click to collapse
Lol I think you over clocked it on the minimum ... try the minimum at 800m ... or if anything flash a new rom.. its probably the rom itself
Sent From In between Your Moms Boobies
Try another (stable) rom? (no development rom)
Wipe everything.
And yes, probably its underclocked/overclocked too high.
I would like to flash a rom but once I turn it on it keeps force closing everything and I am unable to do anything on the phone, It boots into recovery mode just fine though
Sent from my HTC Vision using XDA App
King350z said:
I would like to flash a rom but once I turn it on it keeps force closing everything and I am unable to do anything on the phone, It boots into recovery mode just fine though
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Good news, you flash your ROM from recovery. Download the package, boot into recovery. Mount the SD card and push or push using adb push. Flash the zip from CWM.
my friend purchased the phone yesterday and he is on the latest Official version (2.3.6) and the phone keeps rebooting!!!
is this normal?? there must a problem!
3mar84 said:
my friend purchased the phone yesterday and he is on the latest Official version (2.3.6) and the phone keeps rebooting!!!
is this normal?? there must a problem!
Click to expand...
Click to collapse
Wipe data/factory reset from recovery if it's a used phone.
If he just bought it return it... thats easy
If he rooted it and changed the rom -- put it back to stock or put a new rom on it
I personally found that most of my restarts were due to me trying to pull the stock launcher into an unfamiliar rom. Make sure (if you are using Titanium backup) to only load apps not system *unless you are trying to go back to the same rom*
good luck
First check if he overclocked too much or underclocked too much. Put it to normal.
Alternatively you can just flash another rom. Before flashing remember to wipe everything
Goodluck!
Hey guys. New here been messing with my phone quite a bit and up until now ive been able to fix everything ive broken lol. Im using calkulins ROM 2.8 with hitma kernel and darker orange theme and everything was wonderful. Then somehow after trying to flash an ics theme it borked my recovery. Now when I boot to recovery all I get is the cwm logo screen with version number 5.8.1.5 I think. And it jumps from there straight into booting up normally literally skipping recovery.
Now im in panic mode because I cant fix anything without some kind of recovery to flash with. And I dont have ready access to a PC. So I was hoping someone had a solution to this problem that doesnt require a PC. If not id still like to hear it so I can find a PC and do it. I tried ROM manager too and it just keeps skipping recovery. Thanks in advance you guys are awesome.
Update: never mind guys I found a PC. Factory reset el29. Rerooted using Odin. Nandroid restore and viola. Im liking this cell phone business kinda fun. What do you need to learn to create your own roms/kernels? My interest is peaked now.
Sent from my SPH-D710 using XDA App
I'm still stuck at the Asus eee pad screen and I didn't find a solution for it yet.
did the superwipe and I tried different roms,search in every topic.
I use the correct cwm 3.2.0.1
its driving me mad!Please help!!
How long are you waiting on booting?
Wipe everything, load rom, fix permissions and boot then give it 5 minutes...
Try gnufabios ics rom and watch the progress... does is say completed?
I did a superwipe and fixed permission,I have tryed the revolution rom and the standard with root.
after complete i did a reboot then you see the green bar then it reboots again and I wait for more then half a hour..
why is this happening to me things never go smooth ...
Perhaps try loading this one
http://uploading.com/files/1973838a/us-8.6.5.21-CWM-full-unrooted.zip/
Make sure the power is plugged in.
Hang in there champ, there's a solution somewhere.
thanks! I will try it later on.
hoop it works..
and if it don't do you have some other ideas? ?
I suppose more info would help.
What did you have before ? Revolver? Prime? Stock rooted rom?
If stock ROM, which version?
And which ROM did you try first when the problems started?
Ps: I'm no expert just read a lot of these threads and flashed a few Roms.
at first I had revolver 3.11 (hc) and the first ics rom I tried was the us stock rooted full (option b). I have tried different mirrors.
c-greg said:
I did a superwipe and fixed permission,I have tryed the revolution rom and the standard with root.
after complete i did a reboot then you see the green bar then it reboots again and I wait for more then half a hour..
why is this happening to me things never go smooth ...
Click to expand...
Click to collapse
same thing happened to me too,since the update two times surprisingly i noticed my screen stucked at the Asus logo,i dont know why its so,it looks some issue there in the stability,
but anyway i just did a cold reboot by holding down the volume down button and the power button simuteneously untill cwm options appears on the left corner as well two images on the center then release the buttons,after few seconds the system will reboot normally.
sorry for my poor english...
that sounds like a different problem because you passed the installation process and the system just reboots (there are other with the same problem)I on the other hand am still stuck before that
just try going back to recovery and manually wiping rather than using super wipe - reflash the rom and reboot - dont fix permissions either.
sorry did that already. then people said superwipe is the solution but that didn't work either ..maybe I'm the only one....
Had the same Problem Yesterday.. - with a Restore from a CWM Backup..
Always Stuck @ the EEE PAD Screen.. - Tried Permissions, Wipe Cache, Old Backups etc. but the PAD never Boot..
After this i Flashed "Revolution ICS" and the Problem was gone.. - don´t know why. Maybe the Kernel?!
can you get back to another rom or base?
how much free disk space do you have?
Yes I can i'am now still on revolver 3.11 hc..
Tried the revolution HD rom didn't. Work either.
Very strange.......
try flashing the stock ww full rom with root first to give you an ics base.....
is it rogue recovery you have? if not flash it first and then try working from internal sd.
otherwise im not sure what else to suggest.
I don't know what roque recovery is...
I will try the roque method and some different roms will be back later on..
Sent from my Nexus One using XDA App
Is it normal that while flashing a rom in cwm the bar won't move?it just stays gray..and then complete....
Sent from my Nexus One using XDA App
Yes, thats normals.. Happens every Time here
I tried both Recoverys (Roque and Roach) was always the same ... - Hope Roque Recovery Helps you..
Flashed from External or Internal SD? Try Flashing from Internal so you know your External SD is not corrupt.. - You can flash from Internal only from Roque btw.
I'm getting sick and tired. Even roque won't work flashing it from internal..how long does it normally take to get past the eeepad logo??
Sent from my Nexus One using XDA App
Whenever I attempt to boot up the phone with a custom rom on it, the first boot seems normal and all, but then it will suddenly freeze and not do anything. I have seen threads with this issue but with no answers, and I was hoping I could get some help here. Sorry if I'm lacking details, I'm not super Android savvy. Thanks.
pyr07 said:
Whenever I attempt to boot up the phone with a custom rom on it, the first boot seems normal and all, but then it will suddenly freeze and not do anything. I have seen threads with this issue but with no answers, and I was hoping I could get some help here. Sorry if I'm lacking details, I'm not super Android savvy. Thanks.
Click to expand...
Click to collapse
Do you deleted all user data (Factory reset)?
If no, do that! If the problem appears again, restore your NANDROID backup (You did a backup, didn't you?)
And if the problem isn't gone reflash your firmware using KDZ Updater (Your LG will be unrooted)
Sent from my LG-P500 running JBOne Alpha 2
(Sorry for the late reply)
I've already recovered my phone and apps. When I have the defaut Froyo (rooted) on my phone, it boots fine, but whenever I try to load a custom rom, the first boot-up lasts forever.
Sent from my VM670 using xda app-developers app
Alright, I'm at my wit's end and I've searched the web far and wide. Tonight I thought I'd root, recover and MOD my S5 (have done so before with the S3 and Epic many times).
Ran into a series of problems, but here is where I'm at presently:
I got Philz touch recovery working fine. I used it to install [MOAR][NE5] v2.2 / The Next Level / Wicked Sick / Endless Customization which noted a couple errors (didn't say which) but overall seemed to call the installation a success.
Then I go to restart and I get the Samsung S5 splash, followed by dark screen and reset vibration, the following message:
(blue) RECOVERY BOOTING
(red) RECOVERY IS NOT SEANDROID ENFORCING
(yellow) SET WARRANTY BIT: recovery
which then kicks me back to Philz touch.
Any idea what I can do? I'm glad I can at least get to recovery (and download mode). Hopefully at worst putting stock on the SD and installing that from Philz would solve the problem... but I'm a little pessimistic since the ROM I just installed doesn't seem to work. Thanks for any help, I really appreciate it.
put the stock rom this why i dont mess with my 599.99 phone
You can always Odin back on stock and start over, or flash a different rom.
sersdf said:
Alright, I'm at my wit's end and I've searched the web far and wide. Tonight I thought I'd root, recover and MOD my S5 (have done so before with the S3 and Epic many times).
Ran into a series of problems, but here is where I'm at presently:
I got Philz touch recovery working fine. I used it to install [MOAR][NE5] v2.2 / The Next Level / Wicked Sick / Endless Customization which noted a couple errors (didn't say which) but overall seemed to call the installation a success.
Then I go to restart and I get the Samsung S5 splash, followed by dark screen and reset vibration, the following message:
(blue) RECOVERY BOOTING
(red) RECOVERY IS NOT SEANDROID ENFORCING
(yellow) SET WARRANTY BIT: recovery
which then kicks me back to Philz touch.
Any idea what I can do? I'm glad I can at least get to recovery (and download mode). Hopefully at worst putting stock on the SD and installing that from Philz would solve the problem... but I'm a little pessimistic since the ROM I just installed doesn't seem to work. Thanks for any help, I really appreciate it.
Click to expand...
Click to collapse
I have heard that philz doesn't work right with all base bands and ROMs, that may just be hearsay. Did you do a full wipe before you flashed the ROM?
Sent from my SM-G900P using XDA Free mobile app
Yea, TWRP has been the most reliable for me, not for everyone though and vice versa.
emanuelrv said:
put the stock rom this why i dont mess with my 599.99 phone
Click to expand...
Click to collapse
Fair enough. I actually was happy with just root to remove the bloat but I think I deleted something critically by accident while removing Sprintzone crap.
metalfan78 said:
You can always Odin back on stock and start over, or flash a different rom.
Click to expand...
Click to collapse
Alright, I might try a different recovery (TWRP) first, but if that doesn't work you're right. Thanks.
metalfan78 said:
Yea, TWRP has been the most reliable for me, not for everyone though and vice versa.
Click to expand...
Click to collapse
Yeah, no luck there either (can get into TWRP and flash the ROM but same boot problem). Got a bad feeling I'm bricked, but will try to flash stock through Odin :-/ Thanks
If you can get into recovery or download mode you are not bricked. Odin is your best bet.
What firmware was your phone running? It is possible you don't have the correct firmware installed for the ROM. You could also try reflashing the ROM. Don't worry about the warning you are getting, that shows up because your recovery is not stock.
Sent from my SM-G900P using XDA Free mobile app
drteeths said:
What firmware was your phone running? It is possible you don't have the correct firmware installed for the ROM. You could also try reflashing the ROM. Don't worry about the warning you are getting, that shows up because your recovery is not stock.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
NE5. Hmm, that makes sense, perhaps that was the problem. Ultimately, I Odin-ed to NK4 which solved matters (well, unbricked anyways).
Well good news for you is that MOAR 5.0 has been released.
Sent from my SM-G900P using XDA Free mobile app