[pikachu miui 2.Xy] Reboot from recovery problem - Bravo General

Can anyone tell me why I can't reboot from recovery after installing the latest pikachu miui? I think it has to do with me coming from cm7. Like it might be a kernel issue.
I'll try to answer any questions about the situation. Any help would be appreciated.
Edit: never mind. I reflashed and all is well.

Related

Earpiece doesn't work a few hours after flashing rom! Help!

Can anyone help? I started experiencing the problem with xtr rom and decided to flash a different rom to try and fix. Problem still persists. Tried a nand restore to a previous rom, no luck there either. Right now I'm on FROYO and I love it but it did it again a while after i flashed the rom. Speakerphone works but ear speaker doesn't. Wiped data and dalvik both times. Anyone have any suggestions, I'm desperate! Donation comes to the dev who can figure this out!
If its been happening repeatedly with several roms, i may suggest you roll back your device to stock ROLLBACK FOR ROOT and try rooting and flashing roms again. however it could be a hardware issue with the phone as well but i would give the rollback a shot before returning the phone beings as its practice for what youll have to do before you return it anyway. =)
Willing to give it a try but the link you provided only tells me how to get from stock to rooted. I'm already rooted
Sent from my FroyoEris using XDA App

[SOLUTION] Bootloop when switching from franco to other kernels

Hi All,
I had heard about many people having issues if switching from franco to any other kernel and knew about the solution [ flashing stock kernel / the entire ROM in case of CM before flashing other kernel]. But, unfortunately in my hurry forgot to do it this one time.
Now, forgive me , but the solution I had heard to fix the bootloop always involved using the flashboot to flash to the stock image and then proceeding from there.
Fearing the worst, I tried going to the bootloader mode and then to the recovery mode. Was quite surprised to find that recovery mode was working perfectly fine, so all I had to do was flash the franco kernel zip file.
The phone then rebooted fine without any issues. And I was then able to proceed without any data loss.
Maybe, it was because I hadn't read about this and it was posted earlier. But, thought this information could be useful for newbies. Cheers!! Mods, please delete the thread if the information is widely known . Tried searching but wasn't able to get any specific results other than what I had mentioned.
Hrithan2020 said:
Hi All,
I had heard about many people having issues if switching from franco to any other kernel and knew about the solution [ flashing stock kernel / the entire ROM in case of CM before flashing other kernel]. But, unfortunately in my hurry forgot to do it this one time.
Now, forgive me , but the solution I had heard always involved using the flashboot to flash to the stock image and then proceeding from there.
Fearing the worst, I tried going to the bootloader mode and then to the recovery mode. Was quite surprised to find that recovery mode was working perfectly fine, so all I had to do was flash the franco kernel zip file.
The phone then rebooted fine without any issues. And I was then able to proceed without any data loss.
Maybe, it was because I hadn't read about this and it was posted earlier. But, thought this information could be useful for newbies. Cheers!! Mods, please delete the thread if the information is widely known . Tried searching but wasn't able to get any specific results other than what I had mentioned.
Click to expand...
Click to collapse
Its well known that you need to flash a stock reset kernel after coming from a Franco kernel to another.
Sent from my Nexus 4 using xda premium
nbeebe24 said:
Its well known that you need to flash a stock reset kernel after coming from a Franco kernel to another.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Of course, I know that as is stated clearly in the OP. [ For CM, it would mean reflashing the ROM] But the solution to bootloop in case one forgets to do so, is just going to the bootloader mode-> recovery mode and flashing the franco kernel again.
As stated, only for newbies.

[Q] Wi-Fi refusing to turn on... Help!

I currrently have a Galaxy s5 sm-g900v. Two days ago, I flashed Alliance rom via Safestrap and everything was great until my wifi starting acting dumb. It refuses to turn on, just hangs. I have tried flashing the modem, and Blaze kernel, hoping it would fix it, but no luck. I unrooted and Odin'd back to complete stock, and it STILL won't work. Somebody please give me some pointers on how I can fix it Help would be GREATLY appreciated.
co.purp said:
I currrently have a Galaxy s5 sm-g900v. Two days ago, I flashed Alliance rom via Safestrap and everything was great until my wifi starting acting dumb. It refuses to turn on, just hangs. I have tried flashing the modem, and Blaze kernel, hoping it would fix it, but no luck. I unrooted and Odin'd back to complete stock, and it STILL won't work. Somebody please give me some pointers on how I can fix it Help would be GREATLY appreciated.
Click to expand...
Click to collapse
i would do a clean wipe and flash stock rooted rom.
i had something similar but not as extreme as yours.
i was on ricks rom and it didnt autoconnect and id have to put in the password everytime i connected.
i clean wiped and installed stock rooted 4.4.4 and all is fine.
keep trying different roms if until you find one that works.
FingerBlastJ said:
i would do a clean wipe and flash stock rooted rom.
i had something similar but not as extreme as yours.
i was on ricks rom and it didnt autoconnect and id have to put in the password everytime i connected.
i clean wiped and installed stock rooted 4.4.4 and all is fine.
keep trying different roms if until you find one that works.
Click to expand...
Click to collapse
Youve posted this in two threads and althought it might work it has nothing to do with ricks rom as many others including myself have been using ricks rom flawlessly.. Id say wipe and flash the rom over again fresh and see if that works.. But saying try another rom isnt a good solution when ricks rom works just fine 99% of the time
elliwigy said:
Youve posted this in two threads and althought it might work it has nothing to do with ricks rom as many others including myself have been using ricks rom flawlessly.. Id say wipe and flash the rom over again fresh and see if that works.. But saying try another rom isnt a good solution when ricks rom works just fine 99% of the time
Click to expand...
Click to collapse
Just giving help to those that need it based on my experiences. It just so happens that ive been on ricks rom and i had that issue. Nothing against rick and his rom but thats the situation and thats how i fixed my issues.
I believe when you are using safestrap you are supposed to flash the kernel modules to get Wi-Fi to work. Or am I mistaken about that?
Thanks guys, but I got it working by factory resetting from stock recovery.

A Big thanks for the CM11 Bigpart Project

Hello. originally i wanted to post this in the CM11 thread, but due to the fact that i am a new user, i cannot.
i wanted to thank Zn7mkUKzN1r8aCIV, and all the other developers who contributed the the BigPart project.
the phone is now working great, far better than the CM10 version. it's like a new device.
in my gratitude i would like to upload the files required for the upgrade:
mega.nz/#!19BCUIBL!L0e2-HEsaTOvRnXmyi1n6dYf4nfw-FxrzOeYdfdrIKg
this also includes the Gapps installation file, and the drivers requierd for the device.
Thank you again!
Orof said:
Hello. originally i wanted to post this in the CM11 thread, but due to the fact that i am a new user, i cannot.
i wanted to thank Zn7mkUKzN1r8aCIV, and all the other developers who contributed the the BigPart project.
the phone is now working great, far better than the CM10 version. it's like a new device.
in my gratitude i would like to upload the files required for the upgrade:
mega.nz/#!19BCUIBL!L0e2-HEsaTOvRnXmyi1n6dYf4nfw-FxrzOeYdfdrIKg
this also includes the Gapps installation file, and the drivers requierd for the device.
Thank you again!
Click to expand...
Click to collapse
hi
very good. He resurrected my atrix 4g. thanks.
klecioclayton said:
hi
very good. He resurrected my atrix 4g. thanks.
Click to expand...
Click to collapse
Glad i could help
Thanks Zn7mkUKzN1r8aCIV and polesapart again!
Downloading it now!
Guys, I know the thread is kinda old, but I gotta give it a try as I too want to revive my atrix 4g
I tried to flash CM11 from the original post (http://forum.xda-developers.com/atrix-4g/development/rom-cm-11-android-4-4-4-atrix-bigpart-t2847281), however, when I perform "FASTBOOT flash recovery recovery_olympus_kitkat_bigpart_finalv2.img", the "Android Recovery" crashes when selected from the menu and I get stuck in a loop where it tries to initialize the option unsuccessfully. Can you please shed some light?? I`ve already tried flashing the hporsche32 recovery and still no success...it`s becoming a bit frustrating.
My phone is a bell atrix D00, already rooted and unlocked. I am currently using the NottachTrix rom, and it installed fine from my original cwm-based recovery (v5.0.2.7-atrix5).
The last attempt I made was trying to install the zip from my previously installed and reliable recovery (v5.0.2.7-atrix5), but it fails with "some symlinks failed"...I'm guessing it is due to not having used the bigpart recovery.
[Solved]
MangoShoot said:
Guys, I know the thread is kinda old, but I gotta give it a try as I too want to revive my atrix 4g
I tried to flash CM11 from the original post (http://forum.xda-developers.com/atrix-4g/development/rom-cm-11-android-4-4-4-atrix-bigpart-t2847281), however, when I perform "FASTBOOT flash recovery recovery_olympus_kitkat_bigpart_finalv2.img", the "Android Recovery" crashes when selected from the menu and I get stuck in a loop where it tries to initialize the option unsuccessfully. Can you please shed some light?? I`ve already tried flashing the hporsche32 recovery and still no success...it`s becoming a bit frustrating.
My phone is a bell atrix D00, already rooted and unlocked. I am currently using the NottachTrix rom, and it installed fine from my original cwm-based recovery (v5.0.2.7-atrix5).
The last attempt I made was trying to install the zip from my previously installed and reliable recovery (v5.0.2.7-atrix5), but it fails with "some symlinks failed"...I'm guessing it is due to not having used the bigpart recovery.
Click to expand...
Click to collapse
Hey guys, first of all, thank you Z and P! my atrix is now revived and I can enjoy it once more! what a great job. So far, really stable (although the screen don't light up until de end of some calls). Battery is doing great!
After some reasearch I found out I should be using the hporch32 recovery. Turns out I also needed to flash the hporch32 boot with "fastboot flash boot boot_olympus_kitkat_bigpart_hporch32_finalv2". I know it was silly, but the guides don't really cover this situation....
Anyways, thank you very much for this gift! Hope this helps other noobs!

OxygenOS 3 Black screen after reboot

Hello!
Ever since trying out the first OO3 Beta (3.0.0) I have gotten a weird bug, flashing the ROM works fine and everything works all the way until I reboot my phone. It loads through the bootanimation and then it just has a black screen and you can see the notification bar flash every 5 seconds or so. This issue also come up on the newest 3.0.1 beta.
I've tried different ways of flashing using the modified recovery and the modified supersu (also without the supersu) but I still get the same issue. I've tried different OO3 ROMs as well like Skydragon and CyanOxy but I get the same bug.
I haven't seen anyone post something about the same issue so I figured I'd ask, sorry if this already has been answered and I missed it.
Thanks in advance.
Same happend to me, always get that black screen, try to reboot once you are in it, works for me.
I've tried rebooting a few times and still got the same result, unfortunately.
Thanks for the advice anyways!
Hi,
I'm facing exactly same issue since new OTA update...
Did you manage to fix it?
Hey Endoloris.
I haven't been able to fix it yet unfortunately. I've really tried almost everything at this point which makes me think there's something odd with the hardware, but I don't really know.
I'll update this thread if I fix it.
Have you uninstalled the Google Search app?? Every time I trie to uninstall the Google app I get the same problem. Now I just let it on my phone.
Edit:
Have you flashed the right firmware for OxygenOS 3??
LordHelmchen89 said:
Have you uninstalled the Google Search app?? Every time I trie to uninstall the Google app I get the same problem. Now I just let it on my phone.
Edit:
Have you flashed the right firmware for OxygenOS 3??
Click to expand...
Click to collapse
Yes, I've tried both those options. I've tried pretty much everything. I even tried restoring the phone to stock 2.2.1 and then updating via OTA and I still got the same issue.
So the weird thing is that I get the same issue on the new Paranoid Android ROM released today.
Adhas said:
So the weird thing is that I get the same issue on the new Paranoid Android ROM released today.
Click to expand...
Click to collapse
Really strange...sorry,but Ican't help you then. Maybe you ask one of the devs with pm.
---------- Post added at 04:07 PM ---------- Previous post was at 04:02 PM ----------
Are you realy sure, that you flashed the right TWRP and firmware?? Or do you use a custom kernel.
Sorry, my last ideas...
I did try different firmwares, it didn't work at all with the old ones for obvious reasons. I tried the twrp 3.0.2 Hybrid, a custom recovery when the first Oxygen 3 beta came out (was orange), and I tried the recovery made by Grarak recently. I also tried using stock recovery and flashing.
No custom kernel, I've tried flashing with the modified Supersu but I was thinking that it might be causing the issue so I tried without root and I still got the same result.
In the same boat here, was running official CM, then this happened.

Categories

Resources