Related
I downloaded and installed Rodriguezstyle MiUi rom yesterday, following all the install procedures(the double wipes and what not). But when I go to use it, it sometimes worked and it sometimes would crash and reboot. It was very weird because instead of just rebooting to the os, it would give the Nexus X then, after going no further, reboot again giving the Nexus X and reboot again and so on. This happened with every MiUi rom I installed, but not with the Evil Desire rom I have now. I really like MiUi, do you guys have any fix?
Specs - Nexus One w/ 5.12 Korean Radio
Trying Rods 1.6.6
Have you overclocked it with setcpu? You might want to turn that off and see what happens. I assume you did a complete wipe first btw?
I did wipe and my rom crashes before I can install setcpu
MIUI 0.11.5 + English Pack
I am using MIUI 0.11.5 Deodexed + English Pack. No issues so far. Its perfect.
Why are you making multiple useless threads about this?
@ inferus
could you post the site you got it from. And I have also tired the bundle, which did not work either
MIUI stock
Here you go
http://forum.xda-developers.com/showthread.php?t=789566
I tried all three of those and on every one my phone gets stuck in the boot loop. I have tried everything, factory wiping, cache wiping, dalvik wiping, battery wiping, and clear storage. is there any way I can completely delete the operating system off my phone so I can freshly install the new rom of MiUi. This is bootloop also happens to me when I flash micromod and cyanogen. THIS IS SO FRUSTRATING! does anyone have the same problem too
this static X bootloop also happened a lot on KoR. its based on CM6.0 but maybe this solution will also fix your problem:
http://forum.xda-developers.com/showpost.php?p=8023620&postcount=4383
@pseudoheld
You are the freaken man, however, is this a permanent fix or only temporary?
I spoke too soon, when I do HBoot in the boot loader, sometimes it skips going to the recovery and goes into the boot loop. Is there any way to update the bootloader
paintmandoo3993 said:
I tried all three of those and on every one my phone gets stuck in the boot loop. I have tried everything, factory wiping, cache wiping, dalvik wiping, battery wiping, and clear storage. is there any way I can completely delete the operating system off my phone so I can freshly install the new rom of MiUi. This is bootloop also happens to me when I flash micromod and cyanogen. THIS IS SO FRUSTRATING! does anyone have the same problem too
Click to expand...
Click to collapse
I was not referring to the other links on that post. I installed the stock hosted directly on that post. Also provided a link below for your convenience
http://djmcnz.batteryboss.org/MIUI/deodexed/miui-n1-0.11.5-deodexed-signed-PROPER.zip
And the English pack.
http://forums.miui-dev.com/viewtopic.php?f=5&t=39
i will keep you posted, again
and same problem. Bootloop and whenever I go to the HBoot and try to boot into recovery I get the boot loop again and it wont even enter recovery, I gotta pop the battery
what recovery did you use
UNLOCKED BOOTLOADER REQUIRED
Here it is: TWRP 2.6.3.0
I've tested backing up / restore, wiping, and installing an old backup (from ver. 2.6.0.0) and all seem to work. I also included the flag "HAVE_SELINUX := true" so it should be compatible with the newer 4.3 based ROMs (needs tested).
To install:
Download and unzip file ("img" was a few bytes over the 8mb forum limit)
Code:
fastboot flash recovery XT901-XT907-TWRP-2.6.3.0-recovery.img
BUGS: I have had the screen start very dim. Sometimes restarting the recovery would fix it, otherwise go to settings / screen, and set the timeout short so it goes out. Press power to turn on and it is at full brightness.
Enjoy!!
Thanks to:
TeamWin for TWRP.
Hashcode and Dhacker for STS-Dev Team source.
Djrbliss for unlocking the bootloader & providing root in the first place.
and mattlgroff
Thank you! Just tested it briefly and it works great. Glad the recovery is finally fixed to be able to use ADB. Was unable to use any TWRPs from 2.5.0.0+ as ADB was broken in the recovery.
CM 10.2 Build removed due to errors.
jbaumert said:
OP updated with link for TWRP compiled with CM10.2 sources
Click to expand...
Click to collapse
The recovery built with the 10.2 sources seems to have an issue with mounting the internal storage and sdcard, but the 1st one built is running perfect. I made a flashable zip of the 2.6.3.0 recovery for anyone who wants to simply flash it in recovery.
@mic213, Thanks for the sanity check. Any chance you have tried backup / restore of a 4.3 build?
Sent from my XT901 using Tapatalk 4
I was able to backup with it. Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
netizenmt said:
Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Do you mean when you reboot from TWRP? I noticed that on other builds, but didn't think much of it.
Recovery Tools is a free app on Google Play. Simply download the Recovery IMG. file from this post, and then open the Recovery Tools app. Grant it root, and now you can simply flash the img. file from the app without having to go into fastboot or compress the file into a flash able zip. Once recovery is flashed phone will reboot into whichever recovery is the most recently flashed. About as basic and straight forward as can be.
---------- Post added at 09:34 PM ---------- Previous post was at 09:22 PM ----------
The recovery file works great, only bug after about 4 days of use would be the dim menu screen in recovery. Still very readable even when bug pops up. Thanks for the great upload
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
scottocs said:
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
Edit....ehh maybe. Still working on it.
Click to expand...
Click to collapse
just make sure everything is wiped and that you are using 4.3 Gapps, also look up the SuperSU 1.65 update, some people have had trouble keeping root when rebooting into 4.3. Flash 4.3 ROM then GAPPS followed by SuperSU update, I would suggest running 4.3 on TWRP 2.5 or 2,6 first. Once your able to run 4.3 on one of those, then good ahead and try flashing 2.6.3. If anything on your phone is 4.2 and trying to load onto 4.3 it will never make it far past the boot screen.
Edited because I started rambling and couldn't delete.
Long story short, I have been having issues wiping, installing, and recovering.
I was flashing from a 4.3 ROM to another 4.3 ROM and decided it would be a good idea to wipe internal. Messed me up good.
I went back to 4.2 finally fixed booting issue on getting stuck at boot image. (Wasn't even making it to the boot animation.) I'll wipe everything except internal like I did before and go from 4.2 to 4.3. Last time I did this I didn't have issues.
motoroid7 said:
I'm not sure what I did, but some ROMs suggest that you wipe internal memory. I did this but now I have the issue after installing a ROM and booting it up... playing with it, if I then go to reboot the phone at all I just get stuck on my boot image (not the animation.) This happens on regardless of what ROM I've installed.
I also now can't go back to my backups. They fail on restoring. [Most recent backup was made on 2.5.0.0, previous to that 2.3.2.3]
How do I fix my phone? I'm wondering if I need to fxz back to a rooted stock ROM to fix what's going on?
Click to expand...
Click to collapse
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
RikRong said:
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
Click to expand...
Click to collapse
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
motoroid7 said:
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
Click to expand...
Click to collapse
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Kyles1329 said:
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Click to expand...
Click to collapse
To piggy back on general advice: I found I was having all sorts of problems going from 4.2 to 4.3. What finally did the trick was I wiped Dalvik, System, Cache AND I formatted data. The formatting was what did the trick.
When you wipe in twrp 2.5+ the recovery does not delete data/cache from internal (system) unless user mounts system prior to wipe. Wiping system cache, data, and dalvik cache is a full system wipe. Recommended if switching ROM rather than flashing nightly. This way no files from a AOKP ROM stick around and try to associate with your new CM based ROM.
Sent from my XT907 using Tapatalk 2
Thanks for the advice guys.
I was finally able to successfully getting my phone to work again last night (very early in the AM). It's very strange. I actually had 0 issues going from LiquidSmooth v2.9 to LiquidSmooth v3.0 (4.2 to 4.3). Though it was from the same dev could be part of it. It wasn't until I tried flashing from SlimROM/4.3 to CM10.2 nightly (where I wiped internal memory requiring me to type "yes".) Another thing is strange is even though it was saying I lost root in TWRP, I'm not sure that I ever did, unless TWRP just re-installed it when I reboot recovery automatically... because I finally told it no when asked if I wanted to re-install root? Then I was finally able to get LiquidSmooth v2.9 bootable and stable.
Again, thanks for all the help guys. I just wish I had a little bit understanding what I all did to finally get it to boot up. It was pretty early in the morning... going on 5/6AM. So I was pretty tired doing all of this. I just knew I couldn't let my phone not be up and running by morning.
I did a backup last night, flashed a 4.3 ROM which had reboot issues, and then restored with this version. I had zero issues, unlike when I was trying to restore with the previous version. Thank-you for your work.
It works with the xt902 too. Thanks!
What's the difference between the link in the first post and the one in the fourth? One of the is broken? Which one has been built with the CM10.2 sources?
I'm using a CM10.2 ROM... Which one should I peek?
Thanks!
Well, not a singlle answer after so many views for days, but thank God it doesn't matter anymore, I was able to force the solution for th issue anyways! Issue resolved, if you have updated to 5.0.2 and have rooted your device before or after causing it to lose WiFi, please check out my solution for this issue here, it may very well prove to be your definitive solution. Thanks!
http://forum.xda-developers.com/showpost.php?p=58367424&postcount=96
Here's the direct quoted message:
ajape said:
Installing the 5.0.2 OTA while rooted completely and utterly broke my WiFi. No matter what I tried, I couldn't get Wifi to work again. In the end I gave up, and just did a full factory reset from recovery. My recovery version btw is TWRP 2.8.3, and after installing the ZIP ROM update from the first post of this thread TWRP stayed, I didn't have to install it again. So anyways, I let it boot up and then rebooted back to recovery to root on recovery exit, which caused bootloops for a little while until I used Power+VolDown to go back into recovery and installed the SuperSU 2.45 zip from there. NO MORE PROBLEMS! It's just, PERFECT!!! Finally, no more long waits while booting looking at the logo, no more bootloops, and most importantly: by only using the recovery zips to root and never trying to root from the system or allowing it try to update SuperSU from the Play Store, NO WIFI ISSUES, from the very start all is just perfectly functioning, soooo smooth and really fast! FINALLY!!!!!! Really happy here, so remember, for XT1064 TWRP 2.8.3.0, and SuperSU 2.45 should really do the trick. Good Luck!
Click to expand...
Click to collapse
And here's the link to the actual thread that has the appropriate 5.0.2 Stock ROM flashable ZIP file:
http://forum.xda-developers.com/moto-g-2014/development/rom-stock-rom-t2970427
I'm running LP. After flashing the zip, it boots (after doing the "Android is upgrading" thing), but then if you shut it down/reboot it bootloops. If I wipe cache through recovery, it boots fine again (after doing the "upgrading" thing once again) and works fine till the next shutdown/reboot.
It doesnt work yet, there is no fix either..
Xposed for lollipop is still an alpha version and should not really be used
Sent from my D5803 using XDA Premium HD app
it does work for some people.
http://forum.xda-developers.com/z3-...osed-custom-recovery-lollipop-backup-t3066716
http://forum.xda-developers.com/z3-compact/development/xposed-lollipop-list-modules-t3061563
Bump
If it is any comfort, I have same issue - and yeah, read in other threads some people it is working perfectly.
Out of desperation I even tried factory-reset but still ended up needing to wipe cache/ Dalvik cache like you.
Hopefully, the Dev will soon release a working-for-all version.
For anyone who has the same issue (and is running on the stock ROM): A factory reset through TWRP did not fix the problem for me. I had to reflash the ROM.
illpillow said:
For anyone who has the same issue (and is running on the stock ROM): A factory reset through TWRP did not fix the problem for me. I had to reflash the ROM.
Click to expand...
Click to collapse
you can just manually uninstall xposed, no need to wipe or reflash anything
Installing XPosed worked fine, the problem was the module installer. Even after removing the installer, the device still was looped. Another explanation could be that I was too dump to remove the installer. For anyone else having the problem, you may post how to remove the installer after being in a boot loop.
I managed to get Xposed to work - got rid of the infernal boot loop issue:
Came from rooted KK 5.77
Flashed pre-rooted Lollipop with R/W enabled, based on CE1
Ran 'Byeselinux' for recovery
Flashed 'Xposed.zip'
Installed 'Xposed alpha2'
Above resulting in the boot loop.
Flashed the 3 files directly on top of my setup, wipe cache/ Dalvik cache & reboot as suggested in this thread: http://forum.xda-developers.com/z3/development/lp-mini-deodex-t3076490
Tested by d/l-ing app from Playstore, installed Amplify from Xposed (had already Lolistat, Xperia/AOSP NavBar & Fix Lollipop Memory Leak running/installed), 5 reboots and all is ok.
Update for the readers wh don't want to read the rest of the thread:
I solved 2 issues ("com.android.phone has stopped" was gone after wiping system, and the updating now works smoothly after i realized that the latest firmware is 4.0.3 and not 4.0.2)
The remaining problem is:
But i still get the welcome screen (like i wiped the data) everytime i reboot from twrp
It is not a ROM issue, because during the process i switched from OctOS to lineage and i still get the problem... what can that be???
quick info: TWRP is the most recent (3.0.3-1), firmware is the newest (4.0.3), Lineage is the nightly from Feb 14.
Original post:
Hello there fellow Oneplus users,
I've got some trouble with my 3T. I changed the OS to OctN some weeks ago. Everything was fine, i din't update the first 2 weeklys and when i wanted to update a few days ago (to OCT-N-WEEKLY-20170210-2251-oneplus3.zip) i tried but there was error 7... i don't remember exactly what i did then but when i booted i got the message "com.android.phone has stopped" and i couldn't get the message away (it appeared directly again after clicking ok) in the background the phone wanted to make a fresh setup. i tried a few things out, and the only thing that worked was wiping the cache, dalvik and data and then installing the rom, that was installed before (OCT-N-WEEKLY-20170121-0348-oneplus3.zip)
the next day i thought i could try it again (i hoped it was just coincidence), but make a backup via twrp before. but then same error... So i wanted to restore the backup. It went without errors in twrp, but the booting afterwards took about 15 minutes! After the boot: again the error message and in the background the "set up new phone" screen... even though i did a restore... so again wipe cache/dalvik/data via twrp and re install the old version of the OctOS
Next day after research: maybe i needed to update the firmware (4.0.2). downloaded it but i thought i would wait a little, because i don't have that much time to deal with those problem right now.
So today i decided to give it a try, rebooted to twrp, but then i thougt: "nah, i'll do it another day". So i really did NOTHING in TWRP -> reboot to system -> same old Error (com.android.phone has stopped) and data lost (new phone setup)
Ok: reboot to twrp, flashed the new firmware (no error) tried to flash the new OctOS -> error 7...
I also have the latest LineageOS rom (lineage-14.1-20170214-nightly-oneplus3-signed.zip) on the phone to try out: wiped Cache/Dalvik/Data install Lineage: same error 7...
same with the old OctOS: everything's fine...
Longstory short: what ever i do in twrp doesn't work expect a wiping and reinstalling the same OctOS that worked the last 3 or 4 weeks...
What am i missing? Or is there really something wrong with my phone?
Try to flash the new TWRP, firmware.
and flash the rom with full wipe
svandasek said:
Try to flash the new TWRP, firmware.
Click to expand...
Click to collapse
TWRP is the newest, and (as already mentioned in the text) firmware was renewed during the process without any success.
What do you mean by full wipe? More than Cache, Dalvik and Data?
But still, i have the feeling, that this error is something not very common... I think i might return to complete stock, if the problems continue.
So,
i solved 2 issues ("com.android.phone has stopped" was gone after wiping system, and the updating now works smoothly after i realized that the latest firmware is 4.0.3 and not 4.0.2)
But is Still get the Welcome Screen (like i wiped the data) everytime i reboot from twrp
It is not a ROM issue, because during the provess i switched from OctOS to lineage and i still get the problem... what can that be???
Nobody got any idea?
felixburk said:
Nobody got any idea?
Click to expand...
Click to collapse
It's a TWRP and f2fs problem. You either need to change your data partition to EXT4 and/or update your TWRP to 3.0.4-1
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
GrandMasterB said:
It's a TWRP and f2fs problem. You either need to change your data partition to EXT4 and/or update your TWRP to 3.0.4-1
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
Click to expand...
Click to collapse
Thanks I'll try that out.
Might it help, if i don't set a password for the phone? Or is it not encryption related?
felixburk said:
Thanks I'll try that out.
Might it help, if i don't set a password for the phone? Or is it not encryption related?
Click to expand...
Click to collapse
It's filesystem driver related and nothing to do with the encryption.