Related
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
Is there a complete and idiot proof way to make my X into a lollipop S on AT&T without losing 4g and still able to use the tablet docking?
Thanks in advance to the wizards!
If you are rooted and your bootloader is unlocked .
0. If not, Root it using kingroot or towelroot v2(not v4) and use flashily (from the playstore) to flash cwm or twrp to flash crowlock to unlock the boot loader. (careful to tap recovery and not boot)
1.Back up everything through custom recovery. (Latest Twrp or CWM would be fine)
Optional: If you dont want to lose any of your 4g lte connection use this recovery.(This one will be a black screen so leave it alone for 2 mins then wake it up then you are fine)
-- While at that recovery back up System, Boot and the EFS partition and cache(This recovery has the Efs option, and since the efs partition contains the communication info its best to do that so you cannot lose the bands.)
Great now you have just backed up every thing so now I will say for the next set of steps install Cyanogenmod, preferably 12.1 since cm13 is a bit unstable.
2. --For this to work with the conversion I suggest now you will need to install the latest version of twrp. (That could be found under this link)
*Make sure You put cm12.1 some where you can find when you are going to flash it*
3. Using the newest version of twrp available, flash cm12.1 on to your phone (Great Almost done) (your choice if you want gapps or not)
4. When its booting up and everything is set up put the latest WW firmware in a place you will remember when you flash it. (Also put in crowlock too, since flashing this fw will relock your Bootloader)
5. Once thats done Boot into Twrp and select advanced wipe. Under there Choose to wipe System, Data, and Cache.
6. Now its time to flash that WW firmware, which does take some time.
7. After that, flash crowlock again since your bootloader has been locked again. (Reflash Twrp.img too after that, using the img flashing option and make sure you flash the recovery and not boot)
8. Great Now you can boot and everything should be alright
Optional con't: If you are bothered by the lack of LTE connection at times, flash that other version of twrp I gave you earlier (only if you bothered to back it up before flashing the ww firmware.)
Then you can restore the EFS partition from there. (I didn't need to do that since I live near the city and even if I traveled away I still found my self LTE connection)
Then just reboot your phone and thats it
For future updates refresh your recovery to quarx's twrp, but keep the Adam's n5 recovery to future updates when you lose band 17 and connectivity options.
---------- Post added--------- Previous post was at 10-30-2015 ----------
Credit goes to tjsooley for figuring out this process and the other people who were present during the thread at the time.
cm12.1 did'nt work PAD/Dock or you install cm12.1 for flash Padfone S WW ?? PAD/Dock work correctly with ww Padfone s ???
thanks
colla.paolo said:
cm12.1 did'nt work PAD/Dock or you install cm12.1 for flash Padfone S WW ?? PAD/Dock work correctly with ww Padfone s ???
thanks
Click to expand...
Click to collapse
Flash ww firmware after cm12.1 through twrp and the dock should work again.
The Dock isn't supported on cm12.1 yet. (Stay tuned though it could happen in a couple of months)
When I boot into recovery freezes at the Asus screen. Is there a way to flash cwm with out using a comp or going through recovery mode?
---------- Post added at 05:46 AM ---------- Previous post was at 05:41 AM ----------
wattseb said:
When I boot into recovery freezes at the Asus screen. Is there a way to flash cwm with out using a comp or going through recovery mode?
Click to expand...
Click to collapse
Nvm. Posting that seemed to fix the problem lol.
---------- Post added at 05:50 AM ---------- Previous post was at 05:46 AM ----------
Justatechie said:
If you are rooted and your bootloader is unlocked .
Back up everything through custom recovery. (Latest Twrp or CWM would be fine)
If you dont want to lose any of your 4g lte connection use this recovery.(This one will be a black screen so leave it alone for 2 mins then wake it up then you are fine)
--
Then you can restore the EFS partition from there. (I didn't need to do that since I live near the city and even if I traveled away I still found my self LTE connection)
Then just reboot your phone and thats it
Click to expand...
Click to collapse
The link to the lte recovery is dead.
wattseb said:
When I boot into recovery freezes at the Asus screen. Is there a way to flash cwm with out using a comp or going through recovery mode?
---------- Post added at 05:46 AM ---------- Previous post was at 05:41 AM ----------
Nvm. Posting that seemed to fix the problem lol.
---------- Post added at 05:50 AM ---------- Previous post was at 05:46 AM ----------
The link to the lte recovery is dead.
Click to expand...
Click to collapse
The link is updated for the twrp recovery that supports efs backups.
If you dont know how to flash cm12.1 check this out He recommends cwm recovery
Afterwards after you successfully flash and booted cm12.1 up just flash to the newer version of twrp then install ww firmware.
Works like a charm. I still have to go back and restore the efs to get LTE back but its pretty fool proof. I did have to reflash CM12 after wiping the system partition and then flash the WW zip on top. It acted like it couldnt flash the OS to an empty system partition. But its running and rooted. Waiting on them to release MM for the Padphone S now lol.
wattseb said:
Works like a charm. I still have to go back and restore the efs to get LTE back but its pretty fool proof. I did have to reflash CM12 after wiping the system partition and then flash the WW zip on top. It acted like it couldnt flash the OS to an empty system partition. But its running and rooted. Waiting on them to release MM for the Padphone S now lol.
Click to expand...
Click to collapse
Yes thats what it did with me but it ignored it anyway
to be exact it said "are you sure you want to leave recovery with an empty system partition" funny how I flashed it so I left and it booted it up pretty normally,
I always flash cyanogenmod with an empty system partition, too, eh
next time I booted recovery up after booting system (just to root it with supersu) recovery and left it, the message went away.
How Can I unlock bootloader ATT 11.10.8.16? is posible? help me pls
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
Hi there,
Havin a little issue with my girlfriends i9100. Flashed clockwork recovery and cm12. 1 but somehow the recovery changed to cyanogenmod recovery and i cant seem to get rid of it in order to install gapps. Neither heimdall nor adb did work in order to Flash twrp. Flashify/twrp Manager didnt work for gapps flash either. Any suggestions?
Jogoe said:
Hi there,
Havin a little issue with my girlfriends i9100. Flashed clockwork recovery and cm12. 1 but somehow the recovery changed to cyanogenmod recovery and i cant seem to get rid of it in order to install gapps. Neither heimdall nor adb did work in order to Flash twrp. Flashify/twrp Manager didnt work for gapps flash either. Any suggestions?
Click to expand...
Click to collapse
You could try this:
Download latest cm 11 nightly
In cm recovery got to apply update and flash cm11.
Reboot then in recovery (should be cwm) flash again latest cm 12.1 together with "isorec- twrp recovery 3.0.2-1.zip by the.gangster" in one go (important!)
Then you have latest twrp for flashing anything and also for incrasing partition (System/data) for flashing bigger packages of gapps or cm 13 with gapps (here incrasing System and data partition is a "must")
Sent from my STAIRWAY using XDA-Developers mobile app
---------- Post added at 01:46 PM ---------- Previous post was at 01:41 PM ----------
Just to add: i never tried to flash twrp.zip in cm recovery so i am not sure if it works (would save some Step from above
Sent from my STAIRWAY using XDA-Developers mobile app
Jogoe said:
Hi there,
Havin a little issue with my girlfriends i9100. Flashed clockwork recovery and cm12. 1 but somehow the recovery changed to cyanogenmod recovery and i cant seem to get rid of it in order to install gapps. Neither heimdall nor adb did work in order to Flash twrp. Flashify/twrp Manager didnt work for gapps flash either. Any suggestions?
Click to expand...
Click to collapse
Hi Friend,
CM official roms come with default recovery mode just like the official google roms have there official recoveries cm have.
here is what you will do what you need to do (I use Odin)
NOTE:don't Restart your phone, you have to make the steps from 2 to 4 without restart
1-Install any recovery or kernel from Odin to your mobile (that is the only way to get rid of cm recovery) VERY IMPORTANT!!!
2- open the recovery you installed and flash the rom that you want
3- flash the gapps (optional)
4- flash this file https://dl.twrp.me/i9100/twrp-3.0.2-0-i9100.img (VERY IMPORTANT To Be In The Same Order)
now restart your phone your phone must open now with the new rom, open the recovery mode after the restart to check
VERY IMPORTANT reply to me, I want to know if it worked with you
Thanks,
M.FANDIES said:
Hi Friend,
CM official roms come with default recovery mode just like the official google roms have there official recoveries cm have.
here is what you will do what you need to do (I use Odin)
NOTE:don't Restart your phone, you have to make the steps from 2 to 4 without restart
1-Install any recovery or kernel from Odin to your mobile (that is the only way to get rid of cm recovery) VERY IMPORTANT!!!
2- open the recovery you installed and flash the rom that you want
3- flash the gapps (optional)
4- flash this file https://dl.twrp.me/i9100/twrp-3.0.2-0-i9100.img (VERY IMPORTANT To Be In The Same Order)
now restart your phone your phone must open now with the new rom, open the recovery mode after the restart to check
VERY IMPORTANT reply to me, I want to know if it worked with you
Thanks,
Click to expand...
Click to collapse
Hi
Just want to mention 2 things:
You cannot use any recovery to install cm12 of above. It must be at least a KK compatible recovery.
And not all recoveries can flash .img-files (and the latest version of twrp is 3.0.2-1 of which @the.gangster made a .zip-file for us to use).
Regards
Sent from my ME173X using XDA-Developers mobile app
TriboDoP said:
Hi
Just want to mention 2 things:
You cannot use any recovery to install cm12 of above. It must be at least a KK compatible recovery.
And not all recoveries can flash .img-files (and the latest version of twrp is 3.0.2-1 of which @the.gangster made a .zip-file for us to use).
Regards
Sent from my ME173X using XDA-Developers mobile app
Click to expand...
Click to collapse
sorry for mistakes i have Focused on the Isorec Bec It Have Been a long time from the last time i used it as i have no more i9100
and sure the hard point isnt the compatable recovery it is easy to find and as he have flashed an official cm12.1 rom then he have a working one
am i right or not
thanks,
M.FANDIES said:
sorry for mistakes i have Focused on the Isorec Bec It Have Been a long time from the last time i used it as i have no more i9100
and sure the hard point isnt the compatable recovery it is easy to find and as he have flashed an official cm12.1 rom then he have a working one
am i right or not
thanks,
Click to expand...
Click to collapse
Yes your instructions are correct when using kk recovery and isorec- rec .zip.
Of course there are more ways to do it like by the great @Lanchon in this thread (MOD) IsoRec: Isolated recovery for Galaxy S 2 on Page 53 Post # 529.
Regards
Sent from my STAIRWAY using XDA-Developers mobile app
Thank u guys, i will try and report back next week!
TriboDoP said:
Yes your instructions are correct when using kk recovery and isorec- rec .zip.
Of course there are more ways to do it like by the great @Lanchon in this thread (MOD) IsoRec: Isolated recovery for Galaxy S 2 on Page 53 Post # 529.
Regards
Sent from my STAIRWAY using XDA-Developers mobile app
Click to expand...
Click to collapse
lol thanks! you can actually link posts by right-clicking on the #NNN at the top right corner of each post and selecting "Copy link address"...
http://forum.xda-developers.com/showpost.php?p=69118100&postcount=529
Lanchon said:
lol thanks! you can actually link posts by right-clicking on the #NNN at the top right corner of each post and selecting "Copy link address"...
http://forum.xda-developers.com/showpost.php?p=69118100&postcount=529
Click to expand...
Click to collapse
Thanks!
I never bothered about it but it will save me some typing in the future.
TribodoP
Sent from my STAIRWAY using XDA-Developers mobile app
Anyone here care to share stock firmware? Looking for one and Sammobile's server is down..
---------- Post added at 11:56 AM ---------- Previous post was at 11:42 AM ----------
Disregard the above request.. I've got the download working..
Hi i did a previous thread
http://forum.xda-developers.com/honor-5x/help/os-installed-error-7-t3512747
After that I managed to start Emui and tried to update it
After the update my phone restarted and twrp ran an open recovery script after that when turn on my phone i get honor logo
Im really sorry to start another thread but its not the same problem and i really need help
Calyptos said:
Hi i did a previous thread
http://forum.xda-developers.com/honor-5x/help/os-installed-error-7-t3512747
After that I managed to start Emui and tried to update it
After the update my phone restarted and twrp ran an open recovery script after that when turn on my phone i get honor logo
Im really sorry to start another thread but its not the same problem and i really need help
Click to expand...
Click to collapse
So u installed stock update with twrp right ?
And can u tell me your device model ?
you just followed what isaid right??
you restored a backup that has stock recovery in it..
then how come twrp do anything to you??you sure you didnt uncheck the recovery option while restoring??
---------- Post added at 09:09 AM ---------- Previous post was at 09:06 AM ----------
Calyptos said:
Hi i did a previous thread
http://forum.xda-developers.com/honor-5x/help/os-installed-error-7-t3512747
After that I managed to start Emui and tried to update it
After the update my phone restarted and twrp ran an open recovery script after that when turn on my phone i get honor logo
Im really sorry to start another thread but its not the same problem and i really need help
Click to expand...
Click to collapse
anyway, if you are able access the fastboot, then you got only one way out of this..
just boot into fastboot and flash twrp,
then rebbot recovery and restore again..(make sure the recovery option is selected while restoring menu appears)
and you can boot to emui..
I managed o flash cm thanks forhelping me
Calyptos said:
I managed o flash cm thanks forhelping me
Click to expand...
Click to collapse
good to hear .. GD luck .
Calyptos said:
I managed o flash cm thanks forhelping me
Click to expand...
Click to collapse
finally, you did it!