Related
Hi there,
today i tried to install omar-rom. Booted into CWM-Recovery - data wipe/factory reset, wipe cache, wipe dalvik-cache, mount and format /system. After that i installed the zip and rebooted the device.
And here is my problem, it won't boot properly, first time it boots into system, i see the app optimizing tab and immediately first reboot, after that it reboots while the motologo is shown or while the intel logo is shown... this goes over and over.
Two weeks ago i tried omar-rom, there was no problem. In the last two weaks i used original firmware with infini-ROM, infini-ROM still works when i use my untouched backup with these mods - omar rom doesn't. Tried Omar-Rom from 06.19 and 06.20, same result.
Anybody had similar problems, anybody can help?
PS: Sry 4 my bad english, im not a native speaker.
FourOne82 said:
Hi there,
today i tried to install omar-rom. Booted into CWM-Recovery - data wipe/factory reset, wipe cache, wipe dalvik-cache, mount and format /system. After that i installed the zip and rebooted the device.
And here is my problem, it won't boot properly, first time it boots into system, i see the app optimizing tab and immediately first reboot, after that it reboots while the motologo is shown or while the intel logo is shown... this goes over and over.
Two weeks ago i tried omar-rom, there was no problem. In the last two weaks i used original firmware with infini-ROM, infini-ROM still works when i use my untouched backup with these mods - omar rom doesn't. Tried Omar-Rom from 06.19 and 06.20, same result.
Anybody had similar problems, anybody can help?
PS: Sry 4 my bad english, im not a native speaker.
Click to expand...
Click to collapse
Exactly the same! It goes up to intel logo, then blacks out, sometimes i see optimizing tab, and bootloop.
Then we 2 are doing something wrong - I tried to explain exactly what I did, hope someone know what I did wrong.
But i feel like a retard, so many people use Omar-Rom without problems...
FourOne82 said:
Then we 2 are doing something wrong - I tried to explain exactly what I did, hope someone know what I wrong.
But i feel like a retard, so many people use Omar-Rom without problems...
Click to expand...
Click to collapse
I flashed it once with no problems, might be firmware related... I wipe and install but still it doesn't boot. infini works fine btw
anerik said:
I flashed it once with no problems, might be firmware related... I wipe and install but still it doesn't boot. infini works fine btw
Click to expand...
Click to collapse
exactly the same 4 me here
I did the wipe and factory reset .... then install zip and reboot. I did not put no mount and sistem
Sent from my XT890 using xda premium
First time i installed omar-ROM i did the same, now i tryed some times and nothing works...
if you have backup back .............. and installs another via fastboot and erase everything again had the omar to the days slowly began to return to normal by fastboot
Sent from my XT890 using xda premium
zipi23 said:
if you have backup back .............. and installs another via fastboot and erase everything again had the omar to the days slowly began to return to normal by fastboot
Sent from my XT890 using xda premium
Click to expand...
Click to collapse
What? Can you explain again?
well personally I did download the jellybean eu rom and installed via fastboot or rom pillama deves have usb debugging install . by omar the flash recovery to install any rom do cache factory reset and reboot in cmw
Sent from my XT890 using xda premium
So you think that not installing via fastboot is the problem or what? Because i dont think so, it worked like a charm 2 weeks ago...
zipi23 said:
well personally I did download the jellybean eu rom and installed via fastboot or rom pillama deves have usb debugging install . by omar the flash recovery to install any rom do cache factory reset and reboot in cmw
Sent from my XT890 using xda premium
Click to expand...
Click to collapse
So, you say we use fastboot to return to stock fw and then install the rom as normal, or over pillama?
Flashed stock via RSD-lite, tryed to install omar-ROM with CWM after that - same result, bootloop.
Rryed everything possible now, nothing works - am I stupid or is there a problem with the last versions of omar-ROM?
I'll try flashing it over another firmware, it worked on retail br for me once
EDIT: Bootloop again, got up to optimizing apps and then reboot... This is so weird
I flashed "Retail Central Europe", same result as you mate.
FourOne82 said:
I flashed "Retail Central Europe", same result as you mate.
Click to expand...
Click to collapse
Well we must be doing something wrong lol
Indeed, but what?
Make sure you have a custom recovery installed.
Download the *.zip file to your SD.
Boot into your custom recovery of choice.
<Optional when upgrading same ROM> Data wipe will be required if you came from another ROM, even stock EU.
Select install zip from external card, and choose the zip file.
Hit Reboot.
Sent from my XT890 using xda premium
This is exactly what i did the first time, result bootloop - tested with 2 versions of omar-ROM.
FourOne82 said:
This is exactly what i did the first time, result bootloop - tested with 2 versions of omar-ROM.
Click to expand...
Click to collapse
What about install stock eu version with rsd
Then set up everithing
After, install omars rom without wipe
Intel device - Razr i Owner
Hit thanks if i help you or you like my style
Hi, hoping I haven't done something terrible here.
Rooted Sprint Note 4. Stock other than that, including bootloader
Installed Xposed Installer
then RootCloak module
Xposed Installer: Install->Update
Rebooted directly into a never-ending boot loop (Samsung logo, Sprint logo, reboot).
I was able to get it into recovery once, using a little sh script, but it's not working anymore.
When I was able to get it into recovery, I figured I'd try doing a factory reset, to no avail. Same loop.
I just tried repeatedly pressing a hardware button during boot to disable xposed, no result.
I have the disable .zip file, but no way to push it to the device or flash it, since I can't get into recovery - and even then, it seems I need a custom bootloader to do run it.
I did take an adb backup.
Now, I can only get to the stock Download screen (by holding hardware keys during boot).
Any help? Please?
I'm thinking of flashing this with Odin:
http://forum.xda-developers.com/not...-nie-stockish-knox-root-sprint-stock-t2919346
Hoping that is a reasonable thing to try?
Sigh of relief
OK, I fixed it.. I just redid the same process I did when I first rooted - using cf-auto-root.
And boom! Booted back to stock :victory:
Same issue
blackshawarma said:
ok, i fixed it.. I just redid the same process i did when i first rooted - using cf-auto-root.
And boom! Booted back to stock :victory:
Click to expand...
Click to collapse
having the same issue can fig how fix it?
xcrippleddemonx said:
having the same issue can fig how fix it?
Click to expand...
Click to collapse
Is you're problem with the new Xposed on Lollipop?
not reall sure
ldeveraux said:
Is you're problem with the new Xposed on Lollipop?
Click to expand...
Click to collapse
um its on xposed i honesty dont know if it was lollipop or not i have the note 4 and only updated the firmware once i cant factory reset all i can do is download mode it must be lollipop because it was the uptodate version of xposed
xcrippleddemonx said:
um its on xposed i honesty dont know if it was lollipop or not i have the note 4 and only updated the firmware once i cant factory reset all i can do is download mode it must be lollipop because it was the uptodate version of xposed
Click to expand...
Click to collapse
The first post in the Xposed thread says not to use it on touchwiz UI. Reflash your ROM in ODIN, and wait for Rovo to update Xposed for your system.
Maybe you should check the first posts before flashing something. Samsung roms aren't supported on lollipop
This is a really old post, and people might have already figured this out- HOWEVER, wanam has made a modded version of xposed 87.1 that is supposedly working on TouchWiz ui. Trying now
Here is the problem. I accidentally deleted everything on my Nexus, so now I have no operating system. I am trying to flash stock android 6.0 and I recieve the error "package missing system.img". My phone was already running Marshmallow, and I had no problems installing it the first time, so I am not quite sure why this is happening now.
Majava42 said:
Here is the problem. I accidentally deleted everything on my Nexus, so now I have no operating system. I am trying to flash stock android 6.0 and I recieve the error "package missing system.img". My phone was already running Marshmallow, and I had no problems installing it the first time, so I am not quite sure why this is happening now.
Click to expand...
Click to collapse
easy one to solve as its written around so many times.. do not use the flash-all script, you have to flash each partition individually.
simms22 said:
easy one to solve as its written around so many times.. do not use the flash-all script, you have to flash each partition individually.
Click to expand...
Click to collapse
I did this but it got stuck in a boot animation.
Majava42 said:
I did this but it got stuck in a boot animation.
Click to expand...
Click to collapse
try it again. if you get stuck in a bootloop, go back and wipe data/factory reset.
simms22 said:
try it again. if you get stuck in a bootloop, go back and wipe data/factory reset.
Click to expand...
Click to collapse
I tried this 3 more times and it still got stuck in a bootloop, should I keep trying?
Are you using a toolkit to flash?
Sent from my Nexus 6
Majava42 said:
I tried this 3 more times and it still got stuck in a bootloop, should I keep trying?
Click to expand...
Click to collapse
Try reflashing boot.img.
Worked for me.
Did you ever find a solution to this problem? I'm curious now! I've heard of people having this problem before, I started flashing them individually for this reason! You can NEVER be too safe when doing something like this. You get the hang of doing it individually after doing it so many times though.
Sent from my Nexus 6
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
bfürbanane said:
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
Click to expand...
Click to collapse
Download Odin, using 3.04 or 3.07 for win 7,8,10
http://www74.zippyshare.com/v/18196321/file.html
Put the devices in download mode (Press volume Up + home + power) and install a stock firmware
http://www.sammobile.com/firmwares/database/GT-N7000/
Guide Odin n7000
http://forum.xda-developers.com/showthread.php?t=1424997
If you want to install a custom rom type CM11, CM12 or CM13 you have to install a kernel compatible with recovery
Install PhilZ recovery, then from recovery install a compatible kernel
Kernel CM11
https://www.androidfilehost.com/?fid=24052804347829437
Kernel CM12
http://forum.xda-developers.com/devdb/project/dl/?id=16862
After flashing the kernel do a
Data factory reset
Wipe cache
Wipe Dalvik/ART
Install ROM, install gapps
If it does not work
Data factory reset
Wipe cache
Wipe Dalvik/ART
Format system
Format cache
Format data
Install ROM, install gapps
panamera2011 said:
Download Odin, using 3.04 or 3.07 for win 7,8,10
http://www74.zippyshare.com/v/18196321/file.html
Put the devices in download mode (Press volume Up + home + power) and install a stock firmware
http://www.sammobile.com/firmwares/database/GT-N7000/
Guide Odin n7000
http://forum.xda-developers.com/showthread.php?t=1424997
If you want to install a custom rom type CM11, CM12 or CM13 you have to install a kernel compatible with recovery
Install PhilZ recovery, then from recovery install a compatible kernel
Kernel CM11
https://www.androidfilehost.com/?fid=24052804347829437
Kernel CM12
http://forum.xda-developers.com/devdb/project/dl/?id=16862
After flashing the kernel do a
Data factory reset
Wipe cache
Wipe Dalvik/ART
Install ROM, install gapps
If it does not work
Data factory reset
Wipe cache
Wipe Dalvik/ART
Format system
Format cache
Format data
Install ROM, install gapps
Click to expand...
Click to collapse
I did everything you said. Unfortunately, my device is still stuck at the boot screen. There were no error messages while flashing the roms and no other unusual events.
bfürbanane said:
I did everything you said. Unfortunately, my device is still stuck at the boot screen. There were no error messages while flashing the roms and no other unusual events.
Click to expand...
Click to collapse
This is really strange, try to redo the procedure without installing SuperSU
Sent from my H60-L02 using Tapatalk
panamera2011 said:
This is really strange, try to redo the procedure without installing SuperSU
Sent from my H60-L02 using Tapatalk
Click to expand...
Click to collapse
Where does it say to install SuperSU? How would that be possible when Android is not booting.
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
I'm sorry but it's really strange, never had installation issues with any version of this rom
Have you tried this kernel to install the rom?
https://www.androidfilehost.com/?fid=24052804347829437
Sent from my H60-L02 using Tapatalk
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
Alternatively, Odin a stock rom and look for a philz.zip with compatible baseband. You can enter stock recovery and then flash the philz.zip via update option. This is essentially replacing stock recovery with the custom version. I did this on a naturally occurring bootloop phone and it seems to work, this method also bypasses the yellow triangle warning on boot.
From there, if you want to use other custom roms just remember to wipe /data and /system before installing the kernel, followed by rom itself after a reboot to recovery.
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
Sorry but I confused the message with the MIUI 6.2.12 thread [emoji16]
Sent from my H60-L02 using Tapatalk
AutumQueen92 said:
Alternatively, Odin a stock rom and look for a philz.zip with compatible baseband. You can enter stock recovery and then flash the philz.zip via update option. This is essentially replacing stock recovery with the custom version. I did this on a naturally occurring bootloop phone and it seems to work, this method also bypasses the yellow triangle warning on boot.
From there, if you want to use other custom roms just remember to wipe /data and /system before installing the kernel, followed by rom itself after a reboot to recovery.
Click to expand...
Click to collapse
I tried that. I went to samsung-updates.com and downloaded a version that I believe is compatible with my baseband version. Is there any way to check what baseband version my phone has? Then I flashed with odin and was stuck in a bootloop. I then flashed PhilZ recovery and the boot hangs at the samsung logo.
bfürbanane said:
Is there any way to check what baseband version my phone has?
Click to expand...
Click to collapse
Settings>about phone>
IronRoo said:
Settings>about phone>
Click to expand...
Click to collapse
The phone is not booting.
IronRoo said:
Settings>about phone>
Click to expand...
Click to collapse
Doh! sorry not reading what's in front of me. I did once read that you can get phone number via ADB, maybe the same will work for baseband?
bfürbanane said:
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
Click to expand...
Click to collapse
Have you tried a clean install ? Wiping /system and /data partitions then installing a custom ROM .. This option can be found in philz under install a new ROM ..
N00b... said:
Have you tried a clean install ? Wiping /system and /data partitions then installing a custom ROM .. This option can be found in philz under install a new ROM ..
Click to expand...
Click to collapse
Yes, I tried that. I also tried installing a ROM with a custom kernel that works on my other N7000, but it is still stuck at the boot screen.
bfürbanane said:
Yes, I tried that. I also tried installing a ROM with a custom kernel that works on my other N7000, but it is still stuck at the boot screen.
Click to expand...
Click to collapse
I think i got same problem as you do. Im digging on internet , if i get something ill write here.
Condox18 said:
I think i got same problem as you do. Im digging on internet , if i get something ill write here.
Click to expand...
Click to collapse
Good to know that I am not alone with my problem. Right now, I am out of ideas. I tried everything I could think of. I hope you have more luck than me.
same problem
bfürbanane said:
Good to know that I am not alone with my problem. Right now, I am out of ideas. I tried everything I could think of. I hope you have more luck than me.
Click to expand...
Click to collapse
Check this thread, post 3207 http://forum.xda-developers.com/showthread.php?t=1774208&page=321, u may have eactly same problem as me.
Condox18 said:
Check this thread, post 3207 http://forum.xda-developers.com/showthread.php?t=1774208&page=321, u may have eactly same problem as me.
Click to expand...
Click to collapse
Thanks for the pointer. I subscribed myself to that thread.
Hello guys!
Sorry for bothering you but I am trying to get the framework to work.
After I flash it with TWRP I can't reboot my phone (Samsung galaxy s6 edge) (64-bit) to normal mode anymore, it is stuck on a bootloop to TWRP.
When I try to get out off it I get stuck at the Samsung logo.
I tried different methods of installing the framework but none off them seems to work.
Can I get help please?
Greeting,
Jason
jason_p said:
Hello guys!
Sorry for bothering you but I am trying to get the framework to work.
After I flash it with TWRP I can't reboot my phone (Samsung galaxy s6 edge) (64-bit) to normal mode anymore, it is stuck on a bootloop to TWRP.
When I try to get out off it I get stuck at the Samsung logo.
I tried different methods of installing the framework but none off them seems to work.
Can I get help please?
Greeting,
Jason
Click to expand...
Click to collapse
Which Xposed did you install? Have you tried flashing the uninstaller and wipe caches?
mattzeller said:
Which Xposed did you install? Have you tried flashing the uninstaller and wipe caches?
Click to expand...
Click to collapse
Hello and thank you for answering so quickly!
I used this version: "xposed-v86-sdk23-arm64.zip "
And I had to flash the uninstaller to make my phone work again.
jason_p said:
Hello and thank you for answering so quickly!
I used this version: "xposed-v86-sdk23-arm64.zip "
And I had to flash the uninstaller to make my phone work again.
Click to expand...
Click to collapse
Try Wanam's version of Xposed, works on odex and deodex ROMs
mattzeller said:
Try Wanam's version of Xposed, works on odex and deodex ROMs
Click to expand...
Click to collapse
Still got the same problem, stuck on the logo... :/
EDIT: I think it works.
jason_p said:
Still got the same problem, stuck on the logo... :/
Click to expand...
Click to collapse
How long are you waiting after being stuck on the logo? It can take some time to boot
mattzeller said:
How long are you waiting after being stuck on the logo? It can take some time to boot
Click to expand...
Click to collapse
It works, thanks for your help!
jason_p said:
It works, thanks for your help!
Click to expand...
Click to collapse
No problem