Related
Ok I dont get what I am doing wrong when I flash a custom rom. Its seems the only rom I can flash is the original one toast had with the Super user permission. When i try to flash other roms they just loop on the boot screen. I dont know what I am doing wrong I wipe the cache like it says to do.
Am I missing a step or what someone anyone let me know.
this happens to alot of people. you are not alone!
Wiped cache and user data?
I have tried that I have wiped the first three options on the wipe screen and still loops with every rom but one
Clockwork recovery doesn't wipe dalvik properly from what I hear and that would cause a loo.
I have tried clockwork and and just rebooted my phone into recovery the manual way and that still doesn't do it.
Please put the topic of the thread in the Title. That's what it is for.
Question, you said the Rom that toast first supplied. Have you done nand unlock? Most roms now require the second part to obtain full root. Fresh, damage, etc all require both steps of toasts root.
Wipe cache and data...i use tom manager to get in recovery mode then I wipe everything from there..i don't use rom recovery to wipe...just to get in recovery...
Sent from my PC36100 using Tapatalk
elegantai said:
Question, you said the Rom that toast first supplied. Have you done nand unlock? Most roms now require the second part to obtain full root. Fresh, damage, etc all require both steps of toasts root.
Click to expand...
Click to collapse
Yeah did all that too. idk what to do maybe blow up and start over.
Starting fresh does work wonders sometimes. Do you have a custom recovery flashed to the partition? And have you also double checked to make sure you can successfully remount the system? (just to ensure your name is unlocked, not entirely sure what the problem could be)
So, how do I start from stratch??
Hmmm. Well you could flash a stock Rom with no root and start back at toast's part 1 of rooting..... but I am quite sure you could just repeat part 2 of toasts rooting method. thats what i'd do. Start at part two and redo all of that. Keep that recovery flashed, then do all the wiping and just drop a Rom on your card and install it through reboot recovery command.
Just an update I did the rootinng over this time i used the Simple Root .2. Thats the 1 2 3 click method and that worked for me so now i can flash roms thanks guys
Congratis if you need Rom help let me know. I'm not a dev but I'm a advance user since mytouch 3g came out
Sent from my evo using XDA App
Thanks I am just looking for a good Rom to install. Is there anyway to save apps you download from the market place when switching to a new Rom? Tired of re installing all my apps when I switch roms.
titanium backup
Thanks, do you guys recommend any roms?
thats like asking someone what kind of pants they like
lol. best bet is to go to the dev forum and see which ones you like. Try one try em all
True I am stuck on one for now I really like the Fresh 0.5.3. Its trimmed down and seems fast. There where a couple out there that seemed to bogged down with all the graphics and apps they left on there.
So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.
Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent
ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?
ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.
So I have been trying to get multiple roms to work and it seems as only the TouchWiz roms worked for me (getting LTE) Jellybean wouldn't let me connect to any LTE but gave me data.
So I tried to do a few wipes, I deleted my backups (like an idiot) and now I'm stuck with just being able to get into TWRP.
I get into TWRP factory reset and wipe everything then do a internal wipe and install a rom the rom installs but when i go to reboot the rom it gets stuck at the Samsung Galaxy s4 screen and won't move.
What do I do?
I just want to have a jellybean rom...
I can get into TWRP
How long have you let it boot? The first boot can take a long time.
jd1639 said:
How long have you let it boot? The first boot can take a long time.
Click to expand...
Click to collapse
It was sitting for atleast 7 mins... way too long
and the fist boot was already finished this was the first Reboot after me being on the rom
honeyp0t said:
So I have been trying to get multiple roms to work and it seems as only the TouchWiz roms worked for me (getting LTE) Jellybean wouldn't let me connect to any LTE but gave me data.
So I tried to do a few wipes, I deleted my backups (like an idiot) and now I'm stuck with just being able to get into TWRP.
I get into TWRP factory reset and wipe everything then do a internal wipe and install a rom the rom installs but when i go to reboot the rom it gets stuck at the Samsung Galaxy s4 screen and won't move.
What do I do?
I just want to have a jellybean rom...
I can get into TWRP
Click to expand...
Click to collapse
You need to read about TWRP before using it. You should not be wiping "everything" with it.
honeyp0t said:
It was sitting for atleast 7 mins... way too long
and the fist boot was already finished this was the first Reboot after me being on the rom
Click to expand...
Click to collapse
Can you get into download mode? If so you might want to odin the stock firmware.
jd1639 said:
Can you get into download mode? If so you might want to odin the stock firmware.
Click to expand...
Click to collapse
yeah i can i never used odin before.
if i do this will i be able to re-root? or will it update me to mf3?
EDIT: i just let it sit there and got my old recovery back. im on tw 4.2.2 goldeneye. let me check if i can reboot it without it getting stuck.
EDIT2: ok i just let it reboot and it now reboots fine..
I have read 3 of your posts, you really need to start reading before you go any further...if your phone boots on 4.2.2 GoldenEye, stop there until you find more information on what you are trying to do. If you don't you will for sure be using Odin soon, may want to read up on that also...
Good luck.
BTW, you do not need to make a different thread for every question, go back to one of the threads you started, and ask ALL of your questions there...
Hi guys,
Recently I updated my i9505 to official 4.3 version XXUEMJ7...then i rooted it successfully, flashed philz cwm, it worked...i did a backup, then flashed a mod (lightning effect on lockscreen), turned on the phone. Suddenly my wifi won't work so I decided to do a restore from the backup that i made 10 minutes before that. While it was restoring i noticed that i didnt had enough storage so it skipped few things. When it was successfully restored, I turned my phone on and here are the problems:
When it has booted up i recieved so many errors and fc's like procedure system has stopped, com.google.process.gapps error and so on...
I taught ok, lets delete some HD games to gain space and restore it again. But now there was no cwm or any recovery. I can't use Google Play and every app that uses Google files (youtube, gmail, stock internet browser and even facebook)
I'm not sure if I lost root and/or cwm. My question is how to get it back? What do i need to flash over Odin? Download mode works.
Sent from my GT-I9505 using xda app-developers app
Hello.
I have same problem. Nothing works. I think it's a protected bootloader that will rewrite every custom rom/recovery. I had rom for ~20 days, and was just doing my daily routine, rebooted and lost root and CWM. After this same symptoms occured.
I downloaded XXUEMJ7 prerooted now, and it was only rom that I could flash. Have no custom recovery by now and root works... But probably not for long. What's most important - wifi works. This is partial solution for using your phone while someone smarter will explain us what's going on.
socah said:
Hello.
I have same problem. Nothing works. I think it's a protected bootloader that will rewrite every custom rom/recovery. I had rom for ~20 days, and was just doing my daily routine, rebooted and lost root and CWM. After this same symptoms occured.
I downloaded XXUEMJ7 prerooted now, and it was only rom that I could flash. Have no custom recovery by now and root works... But probably not for long. What's most important - wifi works. This is partial solution for using your phone while someone smarter will explain us what's going on.
Click to expand...
Click to collapse
Thank you. I'll try that.
EDIT: can you give me a link, and you flashed it via Odin?
http://forum.xda-developers.com/showthread.php?t=2250824
In this thread, use "ctrl+f" and write "PDA: XXUEMJ7" There will be prerooted odin flashable link.
By the way, flashing this new knox bootloader with 4.3 was worst thing that I done do my phone. And I'm really pissed off on samsung. Hope some smart devs will solve this someday and we will be able to downgrade or bypass this.
Well, I still get those errors all the time... :crying:
I taught this would remove them, but unfotunately didn't..
Samsungi9OO said:
Well, I still get those errors all the time... :crying:
I taught this would remove them, but unfotunately didn't..
Click to expand...
Click to collapse
Try factory reset
socah said:
Try factory reset
Click to expand...
Click to collapse
Thank you
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Info
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Which partitions are you backing up when creating the nandroid with TWRP?
Heisenberg said:
Which partitions are you backing up when creating the nandroid with TWRP?
Click to expand...
Click to collapse
System, data, boot - Installing the kernel made no difference, the device still corrupted on reboot. and then sometimes at least twice it has soft-bricked
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Already tried it mate, a number of times. no joy.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
XxMORPHEOUSxX said:
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
Click to expand...
Click to collapse
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Xtra-arrow said:
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Click to expand...
Click to collapse
Maybe this will be helpful. I think you have the red level warning like this user. Seems like the exact same situation.
http://forum.xda-developers.com/showthread.php?p=64403982
Turns out it isn't bootlooping. Its taking at least 3 minutes to turn on. It looks like bootlooping. BUt if finally loaded. After doing my uninstalling of aomw system apps. Its rebooted and keeps optimising apps. 2-4 then restarts and does same
Info
Heisenberg said:
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Click to expand...
Click to collapse
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
No it isn't necessary to wipe the userdata partition. No modifications are stored in the userdata partition. It would only be necessary to wipe system, data, cache, and dalvik cache. And probably flash the vendor partition too. Not userdata though.
I had a similar problem when I botched a SU flash, same warning then it would take forever to boot, then the rom would degrade over the next several minutes. I know its not fun to start over, but it was the only thing that cleared all the problems. I didn't want to take more time finding another solution when going back to stock is so simple with this device. Follow the instructions in step #11 of Heisenberg's guide (great guide, I link it to friends a lot). Then start again, I know, not what you wanted to hear. Hope this helps!
I am also in agreement with Heisenberg in regards to the userdata partition.
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Info
Xtra-arrow said:
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Click to expand...
Click to collapse
If you are sure about reason Forget ur Backups.
you should completely install Stock Kernel, Rom, Boot.img >> Back to Stock
But If I remember correctly u did this before...
I just have to say Retry Also Install and use Nexus Root Toolkit
:good:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Xtra-arrow said:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Click to expand...
Click to collapse
Can I ask what gapps are you using? Are you using your google account to recover your apps, or are starting fresh each time?
Sent from my Nexus 6P using Tapatalk
Thanks for your reply. I've actually now narrowed itnright down to a few apps, maybe gapps. Sound recorder, voice recorder app and the google app. Either one or more of these cause my optimising apps bootloop.