Related
Anyone have any hints? The Sprint phone reps were clueless. Since CM wipes the options the reps normally use to get it activated, they couldn't help and told me to take it to a Sprint store. I'm not doing that. How is everyone else upgrading from 2.3.4 to CM7.2 with their service intact?
You have to revert back to stock, activate, then flash the ROM.
aamirani said:
You have to revert back to stock, activate, then flash the ROM.
Click to expand...
Click to collapse
Once I revert back to stock, CWM is gone, so I have no way to flash the CM7.2 rom. Once I reinstall CWM, then flash the CM7.2 rom, I have no service. I've already done this merry-go-round twice.
You only have to flash back to a stock rom(make a backup of stock rom and flash to that via CWM while still unlocked) then try flashing CM again.
w0lf215 said:
You only have to flash back to a stock rom(make a backup of stock rom and flash to that via CWM while still unlocked) then try flashing CM again.
Click to expand...
Click to collapse
Could you break that down for me? As I said, when I flash the stock rom, I lose CWM, so I can't flash CM7.2. Once I put CWM back on it and flash CM7.2, I have no service.
after you root and unlock it you should have a custom recovery even on your stock rom. while you're on your stock rom reboot into recovery and make a backup.
---------- Post added at 12:06 PM ---------- Previous post was at 12:01 PM ----------
then you can wipe everything and flash cm and be good to go
tommyb_ said:
after you root and unlock it you should have a custom recovery even on your stock rom. while you're on your stock rom reboot into recovery and make a backup.
---------- Post added at 12:06 PM ---------- Previous post was at 12:01 PM ----------
then you can wipe everything and flash cm and be good to go
Click to expand...
Click to collapse
now I can't get CWM back on it. It's unlocked and rooted with CWM, but when I try and reboot into recovery mode, it won't stick. I saw the thread about deleting the install-recovery-sh file, but that file doesn't exist on my phone. Something besides that file is wiping CWM and replacing it with the stock recovery.
Hi not allowed to post to developer area, so hope I can get help here. Thought I did everything right, sbf to stock 2.3.4, rooted, used clockworkmod recovery to back up, downloaded cm10, gapps, wiped,everything went to unzip rom and got a sd card error (system 7) had to sbf back to 2.3.4 again and redo everything, formatted sd card with phone, rerooted, downloaded tried again, same error. What did I do wrong?? I thought it would be pretty bulletproof. Used directions and a couple of youtube videos to help.
Kind of afraid to try again because its alot of work to get back. Is the problem with my sd card?, my phone, the downloads?? really want jellybean on my x2 hated the fact we didnt get upgraded to ICS
Any help would be greatly appreciated
don't unzip it, install zips in cwm recovery
see vid https://www.youtube.com/watch?v=zxPvEbdrfKs&feature=youtube_gdata_player
more here http://forum.xda-developers.com/showthread.php?t=1759431
How to install xm10 alpha 2 jelly bean
https://www.youtube.com/watch?v=Itpk...e_gdata_player
Also don't use CWM... use our custom BSR and the CM7 patched BSR when on CM10.
GoClifGo05 said:
Also don't use CWM... use our custom BSR and the CM7 patched BSR when on CM10.
Click to expand...
Click to collapse
good point, but he didn't wipe data and cache in cwm, so it was dx2 bsr or android recovery
edit: so dberryann how did you get to recovery?
sd_shadow said:
good point, but he didn't wipe data and cache in cwm, so it was dx2 bsr or android recovery
edit: so dberryann how did you get to recovery?
Click to expand...
Click to collapse
didnt make it to recovery either time. because I wiped, couldnt get to recovery, stuck on motorola icon, so I sbf'ed back to 2.3.4 and reloaded all my stuff. My two attempts didnt go well. I thought the problem was in the sd card, so I erased it. Should I have formatted it to FAT 32 with Windows 7? didnt
sd_shadow said:
don't unzip it, install zips in cwm recovery
see vid https://www.youtube.com/watch?v=zxPvEbdrfKs&feature=youtube_gdata_player
more here http://forum.xda-developers.com/showthread.php?t=1759431
How to install xm10 alpha 2 jelly bean
https://www.youtube.com/watch?v=Itpk...e_gdata_player
Click to expand...
Click to collapse
Didn't unzip, wrote that wrong, used cwm recovery to install the zip from sd card, then got the error sorry for the confusion
dberryann said:
Didn't unzip, wrote that wrong, used cwm recovery to install the zip from sd card, then got the error sorry for the confusion
Click to expand...
Click to collapse
the point was, that you couldn't have used cwm, because it doesn't work with dx2
we have bsr/system recovery, which looks and works like cwm
the question was how you got to where you wipe data
was it through system recovery app and wall charger or
android recovery through rom manager or boot options
---------- Post added at 10:21 PM ---------- Previous post was at 10:18 PM ----------
in bsr did you select install zip from sdcard? not install update
---------- Post added at 10:26 PM ---------- Previous post was at 10:21 PM ----------
pretty sure a status 7 error, is a apply update error
sd_shadow said:
the point was, that you couldn't have used cwm, because it doesn't work with dx2
we have bsr/system recovery, which looks and works like cwm
the question was how you got to where you wipe data
was it through system recovery app and wall charger or
android recovery through rom manager or boot options
---------- Post added at 10:21 PM ---------- Previous post was at 10:18 PM ----------
in bsr did you select install zip from sdcard? not install update
---------- Post added at 10:26 PM ---------- Previous post was at 10:21 PM ----------
pretty sure a status 7 error, is a apply update error
Click to expand...
Click to collapse
the apk file I used for recovery was: MOTODX2_Bootstrap_signed.apk. is that the one I was supposed to use? Should I be using the patched version? I am on rooted stock 2.3.4 Yes, I selected install zip from sdcard.
not really an answer to my question, how you got to recovery
but yes that's the correct one
the zip may be corrupt, redownload and/or compare md5 checksums
---------- Post added at 10:56 PM ---------- Previous post was at 10:46 PM ----------
md5 checker http://download.cnet.com/md5-checker/3000-2092_4-10410639.html
---------- Post added at 11:06 PM ---------- Previous post was at 10:56 PM ----------
cm10 alpha 2 MD5 Sum: 357688cee005e557de4f1e1f1b81d721
dberryann said:
the apk file I used for recovery was: MOTODX2_Bootstrap_signed.apk. is that the one I was supposed to use? Should I be using the patched version? I am on rooted stock 2.3.4 Yes, I selected install zip from sdcard.
Click to expand...
Click to collapse
tried again with a new sd card... downloaded zip file again, re backed up, checked the md5 got a match, went into recovery with the charger cable, wiped everything, installed zip from sd and got the same error message:
set_perm: some changes failed E:error in /sdcard/cm-10-20121007-unofficial-daytona.zip (Status 7) installation aborted
any ideas?
I don't understand why you are having problems.... from stock 2.3.4 boot into BSR... install CM10, install GApps, then wipe data and cache and reboot......
Just to clarify the bsr should be downloaded.. placed on the root of your SD card, install via a file manager like root explorer or anything similar... you should then have an app called system recovery. Open it and press install recovery, plug into a wall charger and press recovery mode...
Sent from my MB870 using xda premium
If on stock rooted 2.3.4 follow this:
1. Download and install moto dx2 bsr
2. Click on system recovery in app drawer. It should be a grey background with dark grey droid.
3. Click install recovery. Should be first of 3. Select OK when notification says successfuly installed.
4. Plug in charger.
5. Select recovery mode.
6. Phone should power down and then boot into recovery.
7. Use volume controls to scroll down and select "backup and restore" with power button. Then select backup next, then select external.
8.When backup is finished. Wipe cache, dalvik cache and wipe data.
9. Chose install zip from SD card. Then chose install from external ,if that is where you have it.
10. Chose ROM and let install. After installed scroll down to " Go Back" and select.
11. Repeat step 9 and chose gapps package. Let install. After installed scroll down to "Go Back".
12. Select reboot system now.....Enjoy..
NEVER SELECT REBOOT RECOVERY....
Thought you were to wipe data and cache after installing the ROM anand GApps. That's how I've always done it.
Sent from my JB'd X2
I have always wipe before install. Wiping before so you have clean slate when you flash. I don't think it really matters
Sent from my MB870 using xda premium
with a moto phone, it's not a bad idea to wipe before and after
Sent from my MB870 using xda premium
dberryann said:
didnt make it to recovery either time. because I wiped, couldnt get to recovery, stuck on motorola icon, so I sbf'ed back to 2.3.4 and reloaded all my stuff. My two attempts didnt go well. I thought the problem was in the sd card, so I erased it. Should I have formatted it to FAT 32 with Windows 7? didnt
Click to expand...
Click to collapse
You should try the flashable x2 recovery. Leave both on your sd card
Here's are the downloads, the re recovery zips are the flashable bsrs.
http://db.tt/wV38HpHu
Sent from my MB870 using Xparent SkyBlue Tapatalk 2
styleKIMCHEE said:
You should try the flashable x2 recovery. Leave both on your sd card
Here's are the downloads, the re recovery zips are the flashable bsrs.
http://db.tt/wV38HpHu
Sent from my MB870 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Finally got it!! Couldnt play for a few days... Decided to sbf and go from scratch, reroot, backup and install. Went really well thanks for all the help from you guys.
Runs like a charm. Hard to believe that Motorola and Verizon couldnt do the same thing...
dberryann said:
Finally got it!! Couldnt play for a few days... Decided to sbf and go from scratch, reroot, backup and install. Went really well thanks for all the help from you guys.
Runs like a charm. Hard to believe that Motorola and Verizon couldnt do the same thing...
Click to expand...
Click to collapse
It's simple. In your last sentence "couldn't" should simply be replaced with won't. Not worth it to them, buy new stuff... that's their philosophy.
Hello everyone, my EVO LTE is currently running MeanRom and I decided to try out CM10. Well, this is when the nightmares started. I downloaded CM10.0.0 stable with 10/11/2012 and 11/30/12 gapps and no matter what I try, CM10 does not boot. It goes to boot animation but it does not ever finish loading. The steps I took.
1. Download Stable CM10.0.0. (I've redownloaded this 3 times to ensure it's a good download.)
2. Download Gapps (versions list above.)
3. Place both zips on my SD card and also tried internal.
4. Boot into TWRP 2.3.1.0
5. Wipe Factory Reset, Wipe System, Wipe Dalvik.
6. Flash both, CM10.0.0 Jewel.zip AND Gapps.
7. Reboot System.
8. Wait countless minutes for it to load, I get to the CM10 boot animation, but it gets stuck rotating.
What am I doing wrong??? My Phone is S-Off. Any ideas?
Did you remember to flash the boot.img from the CM10 .zip file? It's a very common mistake.
Fuzzy Wuzzy said:
Did you remember to flash the boot.img from the CM10 .zip file? It's a very common mistake.
Click to expand...
Click to collapse
Oh man is this seriously all it is. Lmao.
EDIT: Can you link me to this boot.img? The QBking77 video doesn't mention anything about boot.img.
Sent from my SPH-L710 using Tapatalk 2
its in the rom's zip file. doubleclick on zip and you will see boot.img pull it from there onto computer. i have done this as i am on 1.15 but im getting a sync error with my account.
command for fastboot flash
fastboot flash boot "path to wherever your boot.img is at here"
Ascertion said:
Oh man is this seriously all it is. Lmao.
EDIT: Can you link me to this boot.img? The QBking77 video doesn't mention anything about boot.img.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
http://www.andromods.com/basic-how-...stall-htc-evo-4g-lte-android-41-firmware.html
go to the step where it says "Flashing a custom Jelly Bean ROM on HTC Evo 4G LTE"
Could just use flash image GUI. Check the play store.
Sent from my EVO
??
if you are s-off flashing the boot.img first shouldnt matter much.
I flash the rom by using an application called htc dumlock v2, it flashes your recovery to your boot partition, and you flash the second file to restore it to its original location, but its loaded in boot. So it can then alter the boot partition, and flash the rom without needing to flash it beforehand.
But, again im not sure if im mistaken, but i thought if you were s-off you didnt need to do such things.
---------- Post added at 05:15 PM ---------- Previous post was at 05:06 PM ----------
Forget that i found out just now, Why not download the newest nightly? or kushdecks release? I LOVE paranoid android, and it is also currently working great (with cm10 features in it, and a tablet, hybrid, phablet mode for the device)
If you want to continue attempting the stable CM10 your talking about you could always try HTC dumlock v2, as it works pretty well for me and installing things like this.
Have fun with your phone!
Try the superwipe zip from the themes and apps section. If this was a boot.img issue you shouldnt even get to the boot animation, plus your s-off so that shouldn't be an issue.
It sounds like an incomplete wipe or a bad download.
Sent from my EVO using xda premium
OK, so I successfully S-Off'd this phone using DirtyRacun. I backed up the stock functioning ROM, then went to flash Viperlte 2.2.0. Went through all the Aroma installer options, then went to flash. It breezed through the install process, leaving the phone without any operating system on it (Recovery didn't actually flash anything). Tried both CWM and TWRP, and same results each time.
So, I decided to simply try flashing the boot.img in the downloads for Viperlte 2.2.0 via fastboot, and after doing that, the phone still won't boot, and now whenenver I try to reboot into recovery, recovery flashes for a second, and then screen goes blank and boot loops.
Tried reflashing the stock boot.img and reflashed recoveries, same results each time. I'm at a loss. I don't understand what got messed up by fastboot flashing the boot img.
Any help is greatly appreciated!
Boostjunky said:
OK, so I successfully S-Off'd this phone using DirtyRacun. I backed up the stock functioning ROM, then went to flash Viperlte 2.2.0. Went through all the Aroma installer options, then went to flash. It breezed through the install process, leaving the phone without any operating system on it (Recovery didn't actually flash anything). Tried both CWM and TWRP, and same results each time.
So, I decided to simply try flashing the boot.img in the downloads for Viperlte 2.2.0 via fastboot, and after doing that, the phone still won't boot, and now whenenver I try to reboot into recovery, recovery flashes for a second, and then screen goes blank and boot loops.
Tried reflashing the stock boot.img and reflashed recoveries, same results each time. I'm at a loss. I don't understand what got messed up by fastboot flashing the boot img.
Any help is greatly appreciated!
Click to expand...
Click to collapse
how did you install recovery, the first time you must use adb and flash the recovery.img.
command is: fastboot flash recovery(what ever here).img example: fastboot flash recovery recovery-clockwork-touch-6.0.2.9-fireball.img
Ok, have the phone booting again (flashed ruu, then reflashed the dirtyracun hboot). Question still remains, why did I start bootlooping recovery after flashing the boot.img? And why wouldn't the Rom actually flash in recovery?
Again, any insight is appreciated.
Boostjunky said:
Ok, have the phone booting again (flashed ruu, then reflashed the dirtyracun hboot). Question still remains, why did I start bootlooping recovery after flashing the boot.img? And why wouldn't the Rom actually flash in recovery?
Again, any insight is appreciated.
Click to expand...
Click to collapse
flash the rom then the boot img then boot.
Aldo101t said:
how did you install recovery, the first time you must use adb and flash the recovery.img.
command is: fastboot flash recovery(what ever here).img example: fastboot flash recovery recovery-clockwork-touch-6.0.2.9-fireball.img
Click to expand...
Click to collapse
Yeah, did that. I was in recovery (TWRP) when I tried flashing Viperlte, but it never flashed the Rom after selecting all the options in Aroma. It stated that it did, but there's no way it did. It took less than a second to go from "installing" to "complete".
So, something is funky there.
Boostjunky said:
Yeah, did that. I was in recovery (TWRP) when I tried flashing Viperlte, but it never flashed the Rom after selecting all the options in Aroma. It stated that it did, but there's no way it did. It took less than a second to go from "installing" to "complete".
So, something is funky there.
Click to expand...
Click to collapse
what version of twrp are you using
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
for what it's worth some of the guys had problems, and went back to 2.3.3 and solved the problem, I've never had a problem and i'm running 2.4.4
also you must wipe cache,dalvic, data/factory reset,system
Aldo101t said:
what version of twrp are you using
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
for what it's worth some of the guys had problems, and went back to 2.3.3 and solved the problem, I've never had a problem and i'm running 2.4.4
Click to expand...
Click to collapse
I was on the latest release of TWRP (2.4.4.0). I have a recovery log from when it wouldn't flash the ROM. I'll spare the unnecessary strings, and just post the error itself:
error: file_write: write: I/O error
Installer Error (Status 1)
Edit: Just to add, I just successfully flashed SuperSU on the stock ROM using the same TWRP version (2.4.4.0).
Boostjunky said:
I was on the latest release of TWRP (2.4.4.0). I have a recovery log from when it wouldn't flash the ROM. I'll spare the unnecessary strings, and just post the error itself:
error: file_write: write: I/O error
Installer Error (Status 1)
Edit: Just to add, I just successfully flashed SuperSU on the stock ROM using the same TWRP version (2.4.4.0).
Click to expand...
Click to collapse
well, I don't know for sure i'd try 2.3.3 and see what happens
Aldo101t said:
well, I don't know for sure i'd try 2.3.3 and see what happens
Click to expand...
Click to collapse
I appreciate the suggestions. I'll give a few things a try.
Looks like it was the recovery, afterall. Flashed 2.3.3.0, and the ROM is currently flashing as we speak.
Thanks again!
Boostjunky said:
Looks like it was the recovery, afterall. Flashed 2.3.3.0, and it's currently flashing as we speak.
Thanks again!
Click to expand...
Click to collapse
anytime
Aldo101t said:
what version of twrp are you using
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
for what it's worth some of the guys had problems, and went back to 2.3.3 and solved the problem, I've never had a problem and i'm running 2.4.4
also you must wipe cache,dalvic, data/factory reset,system
Click to expand...
Click to collapse
Hmmm, what's going on here? Aldo101t, do aroma installers work for you on 2.4.4.0? I wonder if its a simple reboot after flashing recovery problem. I need a way to reproduce this.
Sent from my Incredible 4G LTE using Tapatalk 2
mdmower said:
Hmmm, what's going on here? Aldo101t, do aroma installers work for you on 2.4.4.0? I wonder if its a simple reboot after flashing recovery problem. I need a way to reproduce this.
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
I confirm aroma not working on 2.4.4.0 at least on my end.
http://img716.imageshack.us/img716/3192/1362812254888.png
mdmower said:
Hmmm, what's going on here? Aldo101t, do aroma installers work for you on 2.4.4.0? I wonder if its a simple reboot after flashing recovery problem. I need a way to reproduce this.
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
well, i'm not sure. when i tried to flash viper 2.2 i had a problem, but i can't remember what i did now. i used the same recovery, got it installed, i think i restored a stock rom then reflashed viper and it worked, but i'm not sure.
it's been awhile since i've tried to flasn with aroma, so
i just tried flashing viper 2.2, DID NOT WORK, so i miss spoke.sorry
I have also had problems with aroma on several builds of twrp and several builds of cwm. I'm currently on cwm touch and if it fails to install (goes from 7% to done in a few seconds) just try it again till it flashes. Also seems to help me if zips are on the ext SD card. Not sure what's up with this but that's how I got it to work. Seems to be an aroma thing. Regular zips have no problems flashing.
Sent from my Incredible 4G LTE using xda premium
Not sure if I'm the only one that this is happening too i have flashed all MM roms with no success to even get pass boot screen only stays on one plus x boot animation screen. My
recovery is blu spark v12 clean install full wipes and it just wont boot up. Anyone know any solutions to help?
White e1003? I have the original black e1003, no problems with mm roms. There has been a lot of discussion about the white one in the mm topics.
Same for me, white e1003 can't boot MM ROMs.
But as I understand, almost all MM ROMs are based on ashwin007 CM13. So maybe there is just a problem with his kernel or something else in his ROM.
Just let him the time to see what's wrong.
Same here
Hi los1010, same here dude, sorry to say.
I have been in contact with two ROM creators, Sudamod & Cyanpop.
I'm using TWRP 2.8.7.0 Blu_Spark.r8 recovery, this might be the problem, from my experience
What we have come up with (sort of) is that it definitely is a kernel issue. i still think that if i changed my recovery it might work. otherwise the E1003 is the issue here, this model was meant to be only for Chinese huh? then they changed that policy to a European-allowed model. I really don't know. i recently went back to android after some years with ios. Please let me know if you find the resolution. I have to much to do to make it some time soon but i'll update this thread if i succeed.
i think you all should try the twrp recovery by master awesome
mohammedtabish said:
i think you all should try the twrp recovery by master awesome
Click to expand...
Click to collapse
I can't install another recovery for some reason, can't enter recovery after the new one's installed. Do i have to go back to stock recovery to flash a new one?
I've tried every recovery and I'm currently on master awsome TWRP, but it doesn't work.
And anyone tried removing the updator script thing???????
---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------
andlin97 said:
I can't install another recovery for some reason, can't enter recovery after the new one's installed. Do i have to go back to stock recovery to flash a new one?
Click to expand...
Click to collapse
No u can install recovery from fastboot or if phone is booting up then u install rashr and flash the img from that app
mohammedtabish said:
And anyone tried removing the updator script thing???????
---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------
No u can install recovery from fastboot or if phone is booting up then u install rashr and flash the img from that app
Click to expand...
Click to collapse
Dose not work for me, when i tried with rashr it made the recovery go into a bootloop so to speak..
mohammedtabish said:
And anyone tried removing the updator script thing???????
---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------
No u can install recovery from fastboot or if phone is booting up then u install rashr and flash the img from that app
Click to expand...
Click to collapse
What updator script thing ?
The problem is not that it can't flash. Flashing works without problem/error. The problem is that it doesn't boot like if there is no system or kernel. It's just stuck on 1+ logo, never seen animated boot logo (eg cm droid logo).
andlin97 said:
Dose not work for me, when i tried with rashr it made the recovery go into a bootloop so to speak..
Click to expand...
Click to collapse
Can't help you in that bro but I think there might be chances that the recovery images u are downloading might be broken do check md5 checksum and download from other browser
---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------
dadaz007 said:
What updator script thing ?
The problem is not that it can't flash. Flashing works without problem/error. The problem is that it doesn't boot like if there is no system or kernel. It's just stuck on 1+ logo, never seen animated boot logo (eg cm droid logo).
Click to expand...
Click to collapse
Oh!! Now I under stand only thing u can do is reach some dev of Opx like MA(master awesome)
I have this issue as well with a black E1003, just bought it. Doesn't matter what recovery I use. anything based on 6.0 doesn't work, not even recoverys.
mohammedtabish said:
Can't help you in that bro but I think there might be chances that the recovery images u are downloading might be broken do check md5 checksum and download from other browser
---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------
Oh!! Now I under stand only thing u can do is reach some dev of Opx like MA(master awesome)
Click to expand...
Click to collapse
los1010 said:
Not sure if I'm the only one that this is happening too i have flashed all MM roms with no success to even get pass boot screen only stays on one plus x boot animation screen. My
recovery is blu spark v12 clean install full wipes and it just wont boot up. Anyone know any solutions to help?
Click to expand...
Click to collapse
sydeu said:
White e1003? I have the original black e1003, no problems with mm roms. There has been a lot of discussion about the white one in the mm topics.
Click to expand...
Click to collapse
dadaz007 said:
Same for me, white e1003 can't boot MM ROMs.
But as I understand, almost all MM ROMs are based on ashwin007 CM13. So maybe there is just a problem with his kernel or something else in his ROM.
Just let him the time to see what's wrong.
Click to expand...
Click to collapse
mohammedtabish said:
i think you all should try the twrp recovery by master awesome
Click to expand...
Click to collapse
dadaz007 said:
I've tried every recovery and I'm currently on master awsome TWRP, but it doesn't work.
Click to expand...
Click to collapse
mohammedtabish said:
And anyone tried removing the updator script thing???????
---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------
No u can install recovery from fastboot or if phone is booting up then u install rashr and flash the img from that app
Click to expand...
Click to collapse
dadaz007 said:
What updator script thing ?
The problem is not that it can't flash. Flashing works without problem/error. The problem is that it doesn't boot like if there is no system or kernel. It's just stuck on 1+ logo, never seen animated boot logo (eg cm droid logo).
Click to expand...
Click to collapse
Guys i F**** DID IT!!!!!
YES! only thing is that now it says setup wizard has stopped but that's problem nr 2.
God i'm happy. I have the white E1003 Euro version AND IM RUNNING SUDAMOD 6.0!! got them goosebumbs all over me xD
Okay, where to start. Spread this boys. all the people having the problem.
I'm running Onyx costom recovery TWRP r8,
Download these four files Blu_spark r88 CM13, Open Gapps ARM for 6.0, SuperSU 2.67 and Sudamods latest ROM. Lets get going.
First, totally format data, (only when having a working recovery, otherwise, stupid.) wipe dalwik cache, system, data and cache. Transer following files to internal after the wiping. SuperSU 2.67 beta, ROM, Blu_sparkr88 CM13.
Flash kernel, flash rom, flash Gapps, flash kernel once more, wipe cache & dalwik cache and it worked for me. It worked. no longer the oneplus logo. Good luck my fellow Droids, i'll try to fix problem nr.2 it is way more popular so someone must have a fix.
Ok will try this
dadaz007 said:
Ok will try this
Click to expand...
Click to collapse
Regarding setup wizard crashed when you have phone up and running, Fixed that to. Mod the Gapps zip using a PC and remove setup wizard file from CORE, then flash the zip in recovery on phone. Problem nr.3, hardware buttons down on screen does not respond. only the right one which now is back. Huh.
andlin97 said:
Guys i F**** DID IT!!!!!
YES! only thing is that now it says setup wizard has stopped but that's problem nr 2.
God i'm happy. I have the white E1003 Euro version AND IM RUNNING SUDAMOD 6.0!! got them goosebumbs all over me xD
Okay, where to start. Spread this boys. all the people having the problem.
I'm running Onyx costom recovery TWRP r8,
Download these four files Blu_spark r88 CM13, Open Gapps ARM for 6.0, SuperSU 2.67 and Sudamods latest ROM. Lets get going.
First, totally format data, (only when having a working recovery, otherwise, stupid.) wipe dalwik cache, system, data and cache. Transer following files to internal after the wiping. SuperSU 2.67 beta, ROM, Blu_sparkr88 CM13.
Flash kernel, flash rom, flash Gapps, flash kernel once more, wipe cache & dalwik cache and it worked for me. It worked. no longer the oneplus logo. Good luck my fellow Droids, i'll try to fix problem nr.2 it is way more popular so someone must have a fix.
Click to expand...
Click to collapse
Good job! I would guess it's end stk with his latest Blu spark r88 that solved it
Everyone here interested, i suggest you use cyanpop instead, trid to flash it the same way, it works much much better with the onyx. No Gapps problem either.
Maybie it was the format of the partition that did it then. Sounds strange that you can't fastboot another recovery though?
Yes i know, i have tried but it says Remote:dtb not found. I don't know why but could it be the migration from blu_Sparks custom made recocery for onyx to TWRP v12 that screws it up? Do i have to format or wipe anything before? Have tried with rashr and fastboot.
I think what did the trick is "Blu_spark r88 CM13" , thanks