Hi all,
this is my first post on xda and first serious problem for me.
I just installed 3DChainfire to my Canvas 2 colors (jelly bean version which i upgraded to kitkat though company upgrade, 4 GB version) and when it rebooted the device it could never go beyond Android logo screen. I was able to go to stock recovery mode, as i did not installed cwd recovery, and i wiped data and factory reset the phone. It did not help, so i wiped cache partition which did not help too. I am unable to use SPTools as my PC does not install drivers for my phone so unable to connect my phone to PC. However i tried to install drivers manually for the device but it did not help.
I have SD card option though and i will try tonight to flash stock JB ROM, if possible. Will it be possible to flash jelly bean ROM through stock recovery mode? I am also confused that whether i should install JB or KK stock ROM as i had upgraded using KK last time. I am stuck friends. Please reply soon or i will have no other option than to go to service centre.
speedracer426 said:
Hi all,
this is my first post on xda and first serious problem for me.
I just installed 3DChainfire to my Canvas 2 colors (jelly bean version which i upgraded to kitkat though company upgrade, 4 GB version) and when it rebooted the device it could never go beyond Android logo screen. I was able to go to stock recovery mode, as i did not installed cwd recovery, and i wiped data and factory reset the phone. It did not help, so i wiped cache partition which did not help too. I am unable to use SPTools as my PC does not install drivers for my phone so unable to connect my phone to PC. However i tried to install drivers manually for the device but it did not help.
I have SD card option though and i will try tonight to flash stock JB ROM, if possible. Will it be possible to flash jelly bean ROM through stock recovery mode? I am also confused that whether i should install JB or KK stock ROM as i had upgraded using KK last time. I am stuck friends. Please reply soon or i will have no other option than to go to service centre.
Click to expand...
Click to collapse
Never ever install chain fire 3d ...ï installed same problem UK what I did?...flashed only recovery and restored a backup...
---------- Post added at 02:18 PM ---------- Previous post was at 02:17 PM ----------
speedracer426 said:
Hi all,
this is my first post on xda and first serious problem for me.
I just installed 3DChainfire to my Canvas 2 colors (jelly bean version which i upgraded to kitkat though company upgrade, 4 GB version) and when it rebooted the device it could never go beyond Android logo screen. I was able to go to stock recovery mode, as i did not installed cwd recovery, and i wiped data and factory reset the phone. It did not help, so i wiped cache partition which did not help too. I am unable to use SPTools as my PC does not install drivers for my phone so unable to connect my phone to PC. However i tried to install drivers manually for the device but it did not help.
I have SD card option though and i will try tonight to flash stock JB ROM, if possible. Will it be possible to flash jelly bean ROM through stock recovery mode? I am also confused that whether i should install JB or KK stock ROM as i had upgraded using KK last time. I am stuck friends. Please reply soon or i will have no other option than to go to service centre.
Click to expand...
Click to collapse
Use only gl tools. ...http://forum.xda-developers.com/android/apps-games/app-gltools-1-29-t2828630
---------- Post added at 02:23 PM ---------- Previous post was at 02:18 PM ----------
speedracer426 said:
Hi all,
this is my first post on xda and first serious problem for me.
I just installed 3DChainfire to my Canvas 2 colors (jelly bean version which i upgraded to kitkat though company upgrade, 4 GB version) and when it rebooted the device it could never go beyond Android logo screen. I was able to go to stock recovery mode, as i did not installed cwd recovery, and i wiped data and factory reset the phone. It did not help, so i wiped cache partition which did not help too. I am unable to use SPTools as my PC does not install drivers for my phone so unable to connect my phone to PC. However i tried to install drivers manually for the device but it did not help.
I have SD card option though and i will try tonight to flash stock JB ROM, if possible. Will it be possible to flash jelly bean ROM through stock recovery mode? I am also confused that whether i should install JB or KK stock ROM as i had upgraded using KK last time. I am stuck friends. Please reply soon or i will have no other option than to go to service centre.
Click to expand...
Click to collapse
Listen download jellybean or kitkat ...u can't flash a rom through stock recovery I used ctr for kitkat....u can only flash through SP tools...never give ur phone to a service center for software problems...They say motherboard issue always and charge ..its a way of making money...ull find drivers for ur phone sorry I can't help u there but mmx a110/ vcom driver guess should work I'm not sure ...ï don't remember the driver ï used ....just flash after formatting and chill out..everything will be fine if u lose ur imei...use wifi download mobile uncle tools and replace ...
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
Please note ..Flashed only recovery means custom ctr recovery not stock ..u can't restore a backup from stock. ..
Thanks all..but i have already flashed..
Thanks all,
I could not wait for replies so had to rush for more information on the topic. After few hiccups i downloaded and installed drivers for my mobile from this site. Then i used SP tool to flash JB on my device. It all about the order of steps: select scatter file in SP tools, press download, remove battery from bricked mobile, insert battery after 15 secs. , plug through usb cable to pc, files will be flashed automatically, press ok wherever required, a green tick appears which means its done. Then i started my phone and it worked.
Then i had the courage to upgrade to KK FOTA. I saved it on my SD card. And i flashed cwd recovery though mobile uncle tool and flashed rom from custom recovery. But sorry to say but my phone was soft bricked again to logo screen :crying::crying: when i rebooted. I went into cwd recovery and again flashed JB.
Then i downloaded CleanKat to SD Card. Again flashed KKFOTA but after first boot i rebooted this time into recovery and flashed CleanKat..and it has been working.
CleanKat is a great ROM.
Thanks to XDA once again.
All the softwares needed had been downloaded from xda site only.
Searching for graphically efficient ROM..any ideas
Presently i have been searching on fastest ROM on this device. And that too for gaming. Do you guys have any idea about ROM which is best for gaming on this device
Should i start a new thread for this discussion?
I successfully rooted thus t-mobile leon a few weeks ago. I instaed the latest twrp without a problem.. I can not seem to manage a rom flash. The last error i got said invalid zip.. Or zip file corrupt.. I wiped cache and delvic and i also done a clean wipe.. I have been trying to flash cm-12.1-20150906-unofficial-ms345 . also says check md5. No md5 file found. Then reboots back to factory.. Frusterating..
Bender0112 said:
I successfully rooted thus t-mobile leon a few weeks ago. I instaed the latest twrp without a problem.. I can not seem to manage a rom flash. The last error i got said invalid zip.. Or zip file corrupt.. I wiped cache and delvic and i also done a clean wipe.. I have been trying to flash cm-12.1-20150906-unofficial-ms345 . also says check md5. No md5 file found. Then reboots back to factory.. Frusterating..
Click to expand...
Click to collapse
Check md5 of the download before flashing to make sure it matches
Sent from my LG-H901 using Tapatalk
The binary error is due to there being a couple different versions of this phone.
We've got a c50, ms345, and a h345 recovery. The metro pcs ROM is only built to flash on the metro pcs recovery since lollipop looks at the device name and not the hardware set when flashing ROMs on certain recoveries.
here is a recovery that should work.
w w w .android filehost. c o m/?fid=24052804347772357
---------- Post added at 12:20 AM ---------- Previous post was at 12:16 AM ----------
i would also recomend using xenonhd
I have tmobile version and the only twrp that works is the blue twrp from cm 12.1 thread. Itll flash cm and xenonHD and anything else. Must use mpcs version of roms though. I'm on xenonHD and it's smoking fast
Sent from my XenonHD-phone using Tapatalk
So i was flashing Hydrogen Os v2.5 through twrp and since 20 mins the .zip file did not flash so i switched off the phone and when i tried re-installing h2os v2.5 it was again taking longer to flash so i turned the phone off again and this time i installed oxygen os v3.1.0 ,for sometime the phone was in bootloop but when it booted there was no wifi, no network and i found that my phone had no imei number plus unknown baseband, unknown bluetooth also i don't have an efs backup can anyone help me restore my phone to normal once again?
point here.
phorcus said:
So i was flashing Hydrogen Os v2.5 through twrp and since 20 mins the .zip file did not flash so i switched off the phone and when i tried re-installing h2os v2.5 it was again taking longer to flash so i turned the phone off again and this time i installed oxygen os v3.1.0 ,for sometime the phone was in bootloop but when it booted there was no wifi, no network and i found that my phone had no imei number plus unknown baseband, unknown bluetooth also i don't have an efs backup can anyone help me restore my phone to normal once again?
Click to expand...
Click to collapse
Same happened with me phone doesn't boot... Can't install recovery...
Nothing works tried all possible ways like hard reset
what recovery are you guys using?
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
This version works with TWRP 302.2, make sure you are using that.. DO NOT use stock recovery..
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
The ideal way to flash h2os is, flash the rom, flash the debloater, dont flash gapps at all.. boot into the rom, the first boot takes a lot of time so dont worry as long as the phone is not rebooting again and again.. once it boots up go through the setup, dont use oneplus account, then install the google installer apk..
https://www.techmesto.com/install-hydrogen-os-google-apps-oneplus-2/
then follow the procedure written in this link to install gapps.. and you're done.. you can use h2os 2.5 now!
Reverting back to OOS 3.1, I have not tried myself.. Maybe, get into recovery (twrp) do a factory reset first after going into wipe, then go into advanced wipe, wipe everything EXCEPT internal storage.. then flash OOS 302 instead of OOS 3.1, and see if it working with all the connectivity. THIS PROCEDURE IS NOT TESTED BY ME!!
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
zipalign said:
point here.
Click to expand...
Click to collapse
thank you for your help so i was on mokee 7.1 when i flashed only this hydrogen modem v1.1 and when i booted i did not find any volte option, so i went back to latest twrp recovery and tried flashing h2os v2.5 but since 20 minutes i was seeing this ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png ) so i switched off my phone midway and then i installed oxygen os v3.1.0 although it got into a boot loop but when it booted there was no wifi, no imei no, no baseband and many more and when i tried installing mokee or cm14.1 again although they got flashed but when i booted my device i saw oneplus logo and for a few seconds i also saw cm logo and the device continuously kept rebooting in a loop also i am only able to flash oxygen os v3.1.0 that too with no wifi, no imei etc. whereas cm14.1 and mokee wouldnt even boot but they do get flashed and h2os wouldnt even flash , please help :crying:
shravansp24 said:
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
Click to expand...
Click to collapse
thanks for writing out, but i am unable to flash H2OS it is taking forever to install, it just says " patching system image unconditionally " i tried installing it through latest twrp and i tried hybrid recovery too
Rohandd said:
what recovery are you guys using?
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
This version works with TWRP 302.2, make sure you are using that.. DO NOT use stock recovery..
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
The ideal way to flash h2os is, flash the rom, flash the debloater, dont flash gapps at all.. boot into the rom, the first boot takes a lot of time so dont worry as long as the phone is not rebooting again and again.. once it boots up go through the setup, dont use oneplus account, then install the google installer apk..
https://www.techmesto.com/install-hydrogen-os-google-apps-oneplus-2/
then follow the procedure written in this link to install gapps.. and you're done.. you can use h2os 2.5 now!
Reverting back to OOS 3.1, I have not tried myself.. Maybe, get into recovery (twrp) do a factory reset first after going into wipe, then go into advanced wipe, wipe everything EXCEPT internal storage.. then flash OOS 302 instead of OOS 3.1, and see if it working with all the connectivity. THIS PROCEDURE IS NOT TESTED BY ME!!
Click to expand...
Click to collapse
i am using twrp-3.0.2-2-oneplus2.img but h2os takes forever to install, but i did flash h2os v2.5's modem v1.1 before flashing h2os v2.5.
i am also seeing this message in twrp " Failed to mount /system (invalid argument) " please help guys
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
shravansp24 said:
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
Click to expand...
Click to collapse
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Rohandd said:
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Click to expand...
Click to collapse
I didnt try the seraph build.. Will try it! Thank you
phorcus said:
thanks for writing out, but i am unable to flash H2OS it is taking forever to install, it just says " patching system image unconditionally " i tried installing it through latest twrp and i tried hybrid recovery too
Click to expand...
Click to collapse
Yeah itll show that message and will last for 5-10mins.. Hydrogen is very slow to install.. If it lasts longer, try flashing the recovery again and trying it..! Or directly flash cm14.1 to see if its booting
Rohandd said:
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Click to expand...
Click to collapse
can you please check this screenshot ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
shravansp24 said:
I didnt try the seraph build.. Will try it! Thank you
Yeah itll show that message and will last for 5-10mins.. Hydrogen is very slow to install.. If it lasts longer, try flashing the recovery again and trying it..! Or directly flash cm14.1 to see if its booting
Click to expand...
Click to collapse
i reflashed the recovery and installed cm14.1 but then the device gets into boot loop,what's the problem here?
phorcus said:
i reflashed the recovery and installed cm14.1 but then the device gets into boot loop,what's the problem here?
Click to expand...
Click to collapse
Even i got into a bootloop after flashing RR or cm14.1.. Dont know the exact issue..
But installing the new h2os, booting it and then clean flashing cm14.1 solved the bootloop issue..!
shravansp24 said:
Even i got into a bootloop after flashing RR or cm14.1.. Dont know the exact issue..
But installing the new h2os, booting it and then clean flashing cm14.1 solved the bootloop issue..!
Click to expand...
Click to collapse
can you tell me the steps you followed to install h2os? cause when i am installing it, it takes forever to install like i waited for almost 20 mins before giving up, or should i wait more?
and did you get the same message as i got like " failed to mount /dev/block/bootdevice........and so on..... device or resource busy "
check the screenshot here ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
phorcus said:
can you tell me the steps you followed to install h2os? cause when i am installing it, it takes forever to install like i waited for almost 20 mins before giving up, or should i wait more?
and did you get the same message as i got like " failed to mount /dev/block/bootdevice........and so on..... device or resource busy "
check the screenshot here ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
Click to expand...
Click to collapse
1) Got into recovery
2) wipe-advanced wipe-everything except internal storage
3) install-HOS rom
(took around 5 minutes)
4) boot rom and finish initial setup
5) Got into recovery
6) wipe-advanced wipe-everything except internal storage
7) install-cm14.1 rom + gapps
8) boot
Maybe your rom is corrupt, try redownloading and im using latest twrp
shravansp24 said:
1) Got into recovery
2) wipe-advanced wipe-everything except internal storage
3) install-HOS rom
(took around 5 minutes)
4) boot rom and finish initial setup
5) Got into recovery
6) wipe-advanced wipe-everything except internal storage
7) install-cm14.1 rom + gapps
8) boot
Maybe your rom is corrupt, try redownloading and im using latest twrp
Click to expand...
Click to collapse
Thank a lot Bro that worked like a charm the downloaded file was corrupt but i got only one network and i am still on h2os, did you get both networks on cm 14.1?
phorcus said:
Thank a lot Bro that worked like a charm the downloaded file was corrupt but i got only one network and i am still on h2os, did you get both networks on cm 14.1?
Click to expand...
Click to collapse
I got both networks to work in cm14.1 but theyre extremely unstable.. I have my phone in flight mode most of the time to avoid reboots.. Wifi works fine.. The moment you activate the sim, it depends on your luck then.. Mine worked 10mins, sometimes 15, then reboots, again 5-10mins and again reboot(tried official as well as seraph's)
shravansp24 said:
I got both networks to work in cm14.1 but theyre extremely unstable.. I have my phone in flight mode most of the time to avoid reboots.. Wifi works fine.. The moment you activate the sim, it depends on your luck then.. Mine worked 10mins, sometimes 15, then reboots, again 5-10mins and again reboot(tried official as well as seraph's)
Click to expand...
Click to collapse
everything is back to normal on my phone, actually i visited the service center today and they told me that my phone is dead and that i would need to pay 17k to change the motherboard :laugh:
problem here is that H2OS 2.5 messed up all our modems, and who has not made OOS EFS backup via terminal is in trouble now.
when problem popped up in all forums [XDA, and OnePlus one mainly] there have been proposed several solutions, like flashing H2OS modem .zip via recovery, after installing OOS.
so now many users have different scenarios to approach, and a working allwide solution seems not to be found 'til now.
personally I have official TWRP 3.0.2-2 and all my flashings have been made with it.
started from OOS 3.1.0 I had on my phone in the last week, 100% working, then flashed H2OS 2.5. seen the new ROM, decided to get back to something more familiar, so I wiped all and flashed latest nightly of CM13. it was working like a charm, but I had bluetooth issues with my xiaomi mi band [like I always had with OP2 and CM13], so I decided to flash back OOS 3.1.0 wiping data.
OOS 3.1.0 booted up, but without connectivity.
then I realized my modems have been messed up, and started looking for a solution.
the only one I'd try is to fastboot flash OOS 3.0.2 .zip [kindly uploaded by Spannaa], and see if my phone starts working again like it should.
'til now, I will stay with H2OS 2.5 which works perfectly. but when I have time, I'll empty my phone backupping all my stuff [fastboot flashing the .zip mentioned above will wipe userdata too, so I'd lose all my stuff] and try the fastboot thing [I already did it a few months ago, no issues at all].
for those who are in big trouble, that cannot flash anything from recovery, I'd suggest to try to fastoboot flash OOS 3.0.2 with the .zip linked above.
if this solution still doesn't come to an happy ending, then you have to try with the unbrick tool from Qualcomm and see what will happen.
the most important thing is and always will be: don't do anything until you are not aware of what you're actually doing to your phone.
Hi all
I have a Smasung Galaxy note 3 (sm-n9005 htle)
I allready rooted it and installed the TWRP 3.0.2-0. That worked fine.
Now i tried to install some custom rom... it doesent work... it shows me the error 7 ...
so i googled for this error. and found a fix.. so i deleted the first lines in the updater-script... after that i tried it again. But it ditent work. It fails with the massage: could not found the binary file.
I wiped and formated the Smartphone as well.
I spend allready the whole day to install any custom rom...
Im really sad about this... maybe someone can help me.
And sorry for my bad english.
Did you confirm the phone's model # in download before flashing TWRP?
audit13 said:
Did you confirm the phone's model # in download before flashing TWRP?
Click to expand...
Click to collapse
Do you mean, that i downloaded the TWRP for my device model? Yes i did
Otherwise what do you mean?
Before flashing anything, especially if I got the phone used, I boot the phone into download just to confirm that the model # matches the label under the battery.
Only after confirming the model # in download do I start flashing files to the phone.
Does the error 7 happen with all custom ROMs?
audit13 said:
Before flashing anything, especially if I got the phone used, I boot the phone into download just to confirm that the model # matches the label under the battery.
Only after confirming the model # in download do I start flashing files to the phone.
Does the error 7 happen with all custom ROMs?
Click to expand...
Click to collapse
The Modelnumber in the downloadmode and the number under the battery are the same.
Yes i tried maybe five custom roms.
Fail is usually user fails to read instructions .
Error one .
I allready rooted it and installed the TWRP 3.0.2-0. That worked fine.
Now i tried to install some custom rom... it doesent work... it shows me the error 7 ...
Aroma installer does not work and thats why instructions tell you to use the older TWRP .
Instructions .
>>>Get a good recovery. TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
>>>TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
JJEgan said:
Fail is usually user fails to read instructions .
Error one .
I allready rooted it and installed the TWRP 3.0.2-0. That worked fine.
Now i tried to install some custom rom... it doesent work... it shows me the error 7 ...
Aroma installer does not work and thats why instructions tell you to use the older TWRP .
Instructions .
>>>Get a good recovery. TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
>>>TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
Click to expand...
Click to collapse
Thanks for it.
I tried now the TWRP 2.8.7.0. For my device there are two versions. The twrp-2.8.7.0-hlte-4.3.img.tar and twrp-2.8.7.0-hlte-4.4.img.tar.
First i tried now the twrp-2.8.7.0-hlte-4.4.img.tar but still gives me an error :
Updating partition deteils...
... done
Full SELinux support is present.
MTP Enabled
Installing '/external_sd/cm-23.1-20161016-NIGHTLY-hlte.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Can't install this package on top of incompatible data.
Please try another package or run factory reset
E:Error executing updater binary in zip '/external_sd/cm-23.1-20161016-NIGHTY-hlte.zip'
Updating partition details...
...done
The other version of TWRP doesent work. It ends up in a reboot circle.
Try Philz Recovery .
That fails flash a clean stock rom
BUT FIRST
.Installing '/external_sd/cm-23.1-20161016-NIGHTLY-hlte.zip'
Can't install this package on top of incompatible data.
Please try another package <<<< or run factory reset >>>
---------- Post added at 11:57 AM ---------- Previous post was at 11:43 AM ----------
You would be best flashing stock rom through Odin and then if you have problems post exact details .
What rom flashed etc .
JJEgan said:
Try Philz Recovery .
That fails flash a clean stock rom
BUT FIRST
.Installing '/external_sd/cm-23.1-20161016-NIGHTLY-hlte.zip'
Can't install this package on top of incompatible data.
Please try another package <<<< or run factory reset >>>
---------- Post added at 11:57 AM ---------- Previous post was at 11:43 AM ----------
You would be best flashing stock rom through Odin and then if you have problems post exact details .
What rom flashed etc .
Click to expand...
Click to collapse
Hell Yeah!
Thanks a lot it finaly worked with Philz Recovery...
I wiped my phone several times before intsalling the rom... but with Philz Recovery it worked!
Thanks so much! Im really happy now... its not the first device with a custom rom... but the first with problems
Thanks thanks thanks
Hello everyone, first of all am a newbie and I am trying to flash my Note3 with custom rom, I installed twrp using Odin, first I faced an error that Everytime Odin will say pass but phone will boot normal, how ever I find the solution by unchecking auto reboot in Odin, after pass I'll unplug the device, pull off battery then restart and it will get me to term recovery and it works fine afterwards. I tried installing few custom ROMs like magma nx, dark lord x etc but after everything done phone get stuck in bootloop. First I did the same and got stuck then I did a stock rom flash and got the phone working again, how ever I tried flashing again with magma nx and it got away from Samsung logo to pyeongchang edition logo and got stuck there, all the roms I tried give me same error. Am using twrp 2.8.7.0. I had also rooted using SuperSU, how can I get past this? Any help will be appreciated.. thank you
What phone model ??
Bootloop read the thousands of bootloop posts use roms SEARCH THREAD box bootloop .
Difficult to know what you are doing wrong without more information .
Model is a Note 3 N9005,
I have gone through most of the threads but I am not finding a solution yet, as I said :-
1) Installed TWRP using Odin
2) Rooted the device
3)Placed few Custom ROMs in SD
4)Flashed using TWRP (followed instructions)
5) Flashing finished successfully
6) Reboot
7) Bootloop
Stuck here, can I provide any other details?
3)Placed few Custom ROMs in SD
As in what rom one only not multiples .
4)Flashed using TWRP (followed instructions)
Right twrp wrong twrp ??
7) Bootloop
What did rom thread say about bootloop ??
Updated bootloader >>when required .
Magma has full instructions and full faqs .
---------- Post added at 02:02 PM ---------- Previous post was at 01:43 PM ----------
mAGMA
SEARCH THREAD Bootloop
https://forum.xda-developers.com/search/thread/3508672?query=bootloop
FAQ
Q: I have bootloop right after I flash the ROM
2. In first boot, when asked to "Consent for Diagnostic Report", you forgot to uncheck it. As written in OP, you have to "uncheck" the Consent for Diagnostic Report.
To solve it:
1. Power off phone
2. Remove sim card
3. Boot to ROM.
4. Go to settings/general management
5. Disable "Report Diagnostic Info"
6. Power off Device.
7. Insert sim card.
8. Boot up phone and continue using it
Managed to make them work already, thanks for the help bro.. appreciate it
I managed to work around the issue of bootloop bro, it had something to do with the kernal , I already flashed to magma and it is working now, how ever I was curious that each time when I restart the phone, it took a bit time to load up, like note 3 logo first, then magma note 8 logo, then after that it says optimizing apps and actually it shows around 240 apps or so, is it normal or is there any workarounds for the same? (How ever, boots up fine but boot up time is around 7-12 min approx)