i just installed twrp 2.4.1.0 and every time i tried to flash a rom it said that it failed. i looked around the thread and people were having the same problem. they said to go back to 2.3.3.0 so i did. it still wont work. before i installed 2.4.1.0 i was on a version i couldnt flash the 4.2 roms with, i have baked blackbean 6 and used the terminal emulator to update. i just typed su then dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 like it said on the website. and i did rename it to twrp.blob and i got the jb version .blob file.i also still can boot up blackbean. sorry for the trouble im kinda new at this stuff.
I had that too. Problems went away when I unticked "signature verification" or something like that in TWRP (it's in the same screen where you swipe to confirm the flash).
Hope that helps :good:
Ti2 said:
I had that too. Problems went away when I unticked "signature verification" or something like that in TWRP (it's in the same screen where you swipe to confirm the flash).
Hope that helps :good:
Click to expand...
Click to collapse
thanks ill try that
Report back whether it helped
Ti2 said:
Report back whether it helped
Click to expand...
Click to collapse
nope it still dont work. i keep getting error status 7. should i try to reflsah it except use fsatboot. ive been useing terminal emulator for it. and i looked threw the settings in twrp and none of the boxes are checked. in the mount only cache and dalvic are checked.
What bootloader are you on?
Ti2 said:
What bootloader are you on?
Click to expand...
Click to collapse
im on the jellybean bootloader.
What rom are you trying to flash?
Ti2 said:
What rom are you trying to flash?
Click to expand...
Click to collapse
cm 10.1
Status 7 usually means your device Id is not compatible with the ROM you are trying to flash. What ROM are you currently on and where did you DL cm from?
sbdags said:
Status 7 usually means your device Id is not compatible with the ROM you are trying to flash. What ROM are you currently on and where did you DL cm from?
Click to expand...
Click to collapse
I'm getting Status 7 with the latest tf300t ROM from get.cm and the latest TWRP
sbdags said:
Status 7 usually means your device Id is not compatible with the ROM you are trying to flash. What ROM are you currently on and where did you DL cm from?
Click to expand...
Click to collapse
im on blackbean 6 and i got it from the link in the thread
well i think i found the problem i was looking threw my downloads on my pc and i found twrp for the tf300tg. i have the tf300t. and that would explain the error 7 thing with the device id. im downloading the right one right now and ill reply back if it works or not.
yupp that fixed it. i feel dumb now lol
How did you get blackbean 6 to flash,I've been trying to flash 6 for days and keep getting that status7 thing.I don't want blackbean 7 cause directory bind doesn't work with 4.2 jb.I have jb bootloader with newest twrp.My error was the build prop one but I have tf300t and my build prop is tf300t.I've been reading forums for days trying to get the error7 gone.II even deleted the build prop check thing in the script updater in the rom zip file.After doing that I now get status 6 error.I ve tried almost every stock based rom for tf300t and had no problem flashing,even blackbean7 flashes fine.Any help would really be appreciated.Thanks or if anyone knows a work aroundto get directory bind to work with jb 4.2. I have like 27 gigs of game data for all my games
Related
so i've recently picked up my asus tf700 again (after about 6 months of no use) and i know i rooted, upgraded to 4.1.1, and unlocked the device but just don't remember how i did it all. and i'm 90% sure i deleted the stock recovery
what i want to know is how can i upgrade to 4.2.1 ?
can i just follow this guide? http://forum.xda-developers.com/showthread.php?t=2481892
current stats:
android 4.1.1
kernal version 3.1.10
build number jro03c.USepad-10.4.4.23-20121127
gen1mx6 said:
so i've recently picked up my asus tf700 again (after about 6 months of no use) and i know i rooted, upgraded to 4.1.1, and unlocked the device but just don't remember how i did it all. and i'm 90% sure i deleted the stock recovery
what i want to know is how can i upgrade to 4.2.1 ?
can i just follow this guide? http://forum.xda-developers.com/showthread.php?t=2481892
current stats:
android 4.1.1
kernal version 3.1.10
build number jro03c.USepad-10.4.4.23-20121127
Click to expand...
Click to collapse
Yep should be good to go
gen1mx6 said:
so i've recently picked up my asus tf700 again (after about 6 months of no use) and i know i rooted, upgraded to 4.1.1, and unlocked the device but just don't remember how i did it all. and i'm 90% sure i deleted the stock recovery
what i want to know is how can i upgrade to 4.2.1 ?
can i just follow this guide? http://forum.xda-developers.com/showthread.php?t=2481892
current stats:
android 4.1.1
kernal version 3.1.10
build number jro03c.USepad-10.4.4.23-20121127
Click to expand...
Click to collapse
Yes, you can... It is a good guide if you can follow it.. You must make sure that you have the latest bootloader and compatible TWRP.. Those are very important so you are not brick your device... Good luck and ask all the questions that you have before trying to install the TWRP and bootloader...:fingers-crossed:
gen1mx6 said:
so i've recently picked up my asus tf700 again (after about 6 months of no use) and i know i rooted, upgraded to 4.1.1, and unlocked the device but just don't remember how i did it all. and i'm 90% sure i deleted the stock recovery
what i want to know is how can i upgrade to 4.2.1 ?
can i just follow this guide? http://forum.xda-developers.com/showthread.php?t=2481892
current stats:
android 4.1.1
kernal version 3.1.10
build number jro03c.USepad-10.4.4.23-20121127
Click to expand...
Click to collapse
Hallo,
could you send me a complete manual how did you root it and updated it for 4.1.1. with all of links for tools? I have a problem with my TF700 and I checked a lot of forums and tried a lot of things but it doesnt help.
Thank you very much
andre776655 said:
Hallo,
could you send me a complete manual how did you root it and updated it for 4.1.1. with all of links for tools? I have a problem with my TF700 and I checked a lot of forums and tried a lot of things but it doesnt help.
Thank you very much
Click to expand...
Click to collapse
you should probably create your own post so someone can help you, they need to know information like what version your currently running
LetMeKnow said:
Yes, you can... It is a good guide if you can follow it.. You must make sure that you have the latest bootloader and compatible TWRP.. Those are very important so you are not brick your device... Good luck and ask all the questions that you have before trying to install the TWRP and bootloader...:fingers-crossed:
Click to expand...
Click to collapse
ok so i'm having a bit of trouble following this guide...
1) I installed TWRP (with the help of this page) http://www.teamw.in/project/twrp2/105 I had to use the Download - Recovery Image / Fastboot Method because the app method wouldn't download the blob file
2) Now, when I power + volume down boot I can see my bootloader isn't the correct version. how can I update the bootloader? I have the files from the original link i posted (http://forum.xda-developers.com/showthread.php?t=2481892) so there is the correct bootloader i just don't know how to install it.
is there a more detailed guide with actual step by steps?
Congrats on getting TWRP installed! The rest is easy.
In TWRP select 'Install' and navigate to wherever you have the zip file with the bootloader/TWRP package, select it (if it has xxx signed.zip in the file name you need to check the "verify zip signature" option. sbdags usually signs his zips - don't know if he did with this one).
Swipe the button to flash the file.
When it finished, boot back to system. Do not flash a rom at this point! That would cancel the bootloader flash. Boot back into system first, then back into TWRP and then flash the rom.
BTW - flashing the modified Asus stock rom is perfectly fine, but I wonder why you don't flash CROMi-X 5.2.2?
That rom is from the same developer, based on this stock rom and miles improved since sbdags debloated the stock version.
sbdags stock rom is not really supported whereas he puts out a better version of CROMi-X about every 10 days! It's exhausting to keep up! LOL
You'll find it here: http://forum.xda-developers.com/showthread.php?t=2425383
You can still flash the BL/TWRP package you downloaded already. It's the same as the one for CROMi-X.
LetMeKnow said:
Yes, you can... It is a good guide if you can follow it.. You must make sure that you have the latest bootloader and compatible TWRP.. Those are very important so you are not brick your device... Good luck and ask all the questions that you have before trying to install the TWRP and bootloader...:fingers-crossed:
Click to expand...
Click to collapse
berndblb said:
Congrats on getting TWRP installed! The rest is easy.
In TWRP select 'Install' and navigate to wherever you have the zip file with the bootloader/TWRP package, select it (if it has xxx signed.zip in the file name you need to check the "verify zip signature" option. sbdags usually signs his zips - don't know if he did with this one).
Swipe the button to flash the file.
When it finished, boot back to system. Do not flash a rom at this point! That would cancel the bootloader flash. Boot back into system first, then back into TWRP and then flash the rom.
BTW - flashing the modified Asus stock rom is perfectly fine, but I wonder why you don't flash CROMi-X 5.2.2?
That rom is from the same developer, based on this stock rom and miles improved since sbdags debloated the stock version.
sbdags stock rom is not really supported whereas he puts out a better version of CROMi-X about every 10 days! It's exhausting to keep up! LOL
You'll find it here: http://forum.xda-developers.com/showthread.php?t=2425383
You can still flash the BL/TWRP package you downloaded already. It's the same as the one for CROMi-X.
Click to expand...
Click to collapse
Thanks, Honestly whatever custom rom I have now can randomly reboot and i think is giving me touch screen issues so was just going to hit up a stock install and see if that fixes any problems.
gonna try out the rom you suggested and i can always go back if necessary.
one thing, when i installed theTWRP the blue bar filled up completely and i left it for about 10 minutes and it was still there. so i powered down and everything booted back up correctly (and i can get into the recovery mode).
does everything sound ok to proceed?
gen1mx6 said:
Thanks, Honestly whatever custom rom I have now can randomly reboot and i think is giving me touch screen issues so was just going to hit up a stock install and see if that fixes any problems.
gonna try out the rom you suggested and i can always go back if necessary.
one thing, when i installed theTWRP the blue bar filled up completely and i left it for about 10 minutes and it was still there. so i powered down and everything booted back up correctly (and i can get into the recovery mode).
does everything sound ok to proceed?
Click to expand...
Click to collapse
You have to kick it out when it is completed by using the fastboot command or just using your power button.. So you are good to go...
You have to try out all the rom and kernels that are available then choose the best one that fit your need...Good luck...
LetMeKnow said:
You have to kick it out when it is completed by using the fastboot command or just using your power button.. So you are good to go...
You have to try out all the rom and kernels that are available then choose the best one that fit your need...Good luck...
Click to expand...
Click to collapse
thanks for the help, everything is complete and running correctly.
I've got myself (and my tablet) into a complete mess.
When I got my tablet it was already unlocked and running ICS (I think).
I decided it was time to upgrade to cyanogenmod Kit Kat.
I started with this tutorial: http://wiki.cyanogenmod.org/w/Install_CM_for_tf700t
I flashed the custom recovery : "recovery-jb-644"
I chose "cm-10.2.0-tf700t" as I was nervous about the nightly. Something went wrong.
The tablet started but crashed after a few minutes and rebooted. I added "gapps-jb-20130813-signed" - it was worse - now the keyboard also crashed.
After that, I tried numerous things to recover it.
Now, I cant access it through the fastboot - it gives the serial number but won't push anything or flash anything.
I put the following on an sd card and tried to install from there but I get:
status 7 assert failed: write_raw_image (" /tmp/blob" , "staging )
or any number of similar messages. I tried the solution here: http://forum.xda-developers.com/showthread.php?t=1235724 which worked once but not again.
My current situation:
The picture attached shows the current installation - it will boot - I have no Google Apps - and it crashes within a minute and then reboots.
I'm not a complete newbie, but I cant find a simple explanation of what to do next.
I just want the tablet to work again, I don't care anymore if its Kit Kat, ICS, Jelly Bean or Honeycomb.... I even considered Linux...
Please help.
Apparently you missed the big fat red warning on the tutorial you linked. You need to install a 10.6.1.14.x bootloader.
(And you need to make sure your recovery is compatible with that bootloader, otherwise you risk a hard brick when you wipe data).
fivaics logical
_that said:
Apparently you missed the big fat red warning on the tutorial you linked. You need to install a 10.6.1.14.x bootloader.
(And you need to make sure your recovery is compatible with that bootloader, otherwise you risk a hard brick when you wipe data).
Click to expand...
Click to collapse
OK, so I've downloaded it, but I still can't install it because of the
status 7 assert failed: write_raw_image (" /tmp/blob" , "staging )
How do I get around this?
I attach a copy of the log showing what happens when I try.
ymget said:
OK, so I've downloaded it, but I still can't install it because of the
status 7 assert failed: write_raw_image (" /tmp/blob" , "staging )
How do I get around this?
I attach a copy of the log showing what happens when I try.
Click to expand...
Click to collapse
According to the page you linked, you are supposed to download a blob file and flash it via fastboot:
http://wiki.cyanogenmod.org/w/Install_CM_for_tf700t#Update_Bootloader_To_Compatible_Version
You didn't say yet in which way fastboot didn't work for you.
Hi,
Thank you for replying.
I can't do "fastboot -i 0x0B05 flash staging XX_bootloaderblob"
When I am in the CMD window, I can do fastboot devices and it see's my serial number, but as soon as I want to actually do something, it tells me the device is not available.
The same goes for any adb commands I want to do.
The only way I found of doing it is through the sideload, but now even this doesnt work.
Hi Again,
Your comment gave me an idea - I did the bootloader fastboot through the sideloader - and it worked!!!
I then added the "gapps-jb-20130813-signed" and now it is crashing on the setup wizard.... and the keyboard crashes.
Any ideas?
ymget said:
Hi Again,
Your comment gave me an idea - I did the bootloader fastboot through the sideloader - and it worked!!!
I then added the "gapps-jb-20130813-signed" and now it is crashing on the setup wizard.... and the keyboard crashes.
Any ideas?
Click to expand...
Click to collapse
Did you reboot after flashing the bootloader and before flashing gapps?
berndblb said:
Did you reboot after flashing the bootloader and before flashing gapps?
Click to expand...
Click to collapse
Yes, I had to check to make sure that the new bootloader worked and the tablet was no longer crashing before I installed the gapps.
ymget said:
Yes, I had to check to make sure that the new bootloader worked and the tablet was no longer crashing before I installed the gapps.
Click to expand...
Click to collapse
I really have no idea... I just checked - you did flash the gapps package for CM 10.2 and I assume you also checked the box "verify zip signature" in your recovery before you flashed gapps?
If not, it maybe as simple as a bad download....
berndblb said:
I really have no idea... I just checked - you did flash the gapps package for CM 10.2 and I assume you also checked the box "verify zip signature" in your recovery before you flashed gapps?
If not, it maybe as simple as a bad download....
Click to expand...
Click to collapse
You were right!! I downloaded the gapps again and now I have a perfectly working tablet.
Thank you to everyone who answered me and helped - you guys are amazing!!
ymget said:
You were right!! I downloaded the gapps again and now I have a perfectly working tablet.
Thank you to everyone who answered me and helped - you guys are amazing!!
Click to expand...
Click to collapse
:GOOD: Glad you got it working! BTW, there's a "Thanks" button for a reason
berndblb said:
:GOOD: Glad you got it working! BTW, there's a "Thanks" button for a reason
Click to expand...
Click to collapse
I know there is supposed to be one - I've read about it - but I can't find it anywhere!!!!
Found it!!!
Anybody figure out how to fix this? I can find people having this problem flashing 4.4 but I can't flash anything. I've tried to flash mf1 firmware, a 4.3 carbon nightly, and a 4.3 pac nightly. All with the same results. Here is exactly what I did -
I flashed PhilZ recovery earlier on a earlier version of TWRP.
kept getting a "failed" in PhilZ
Flashed latest TWRP via Odin
Tried flashing the above mentioned zips all with the error message.
Restored my hyper drive rls16 backup (4.1.2)
Installed latest TWRP via goomanager app
Edit : my phone is flashed to PagePlus so I kinda have to be careful I'm afraid of using Odin to go back to stock/rooted but my luck that's what it'll take. When I get home I'm going to try it with a older version of TWRP that's the only other thing I can think to try.
Any suggestions or info is appreciated.
delete
anyone ? please ?
Supposedly the update binary here is generic, you could try replacing the one in the rom zip with it
http://forum.xda-developers.com/showthread.php?t=2492496
Sent from my SCH-I535 using XDA Premium 4 mobile app
I've tried CWM PhilZ and TWRP all latest versions, and still can't get rid of this.
I Cannot install any rom, whatsoever. I did manage to install a MF1 radio zip, but that's it. I can't install 4.3 or even 4.2 ..
I've replaced the update-binary inside the zips, and edited the update-script and removed the stuff used for recognizing the device, still no dice ..
I ended up flashing a full mf1 img via Odin and then used casual to root/unlock/recovery install - and I STILL get the error. Not sure where to go from here. Seems like nobody else is having this problem unless they're not on the latest recovery and trying to flash KitKat.
Thought I'd share the rest of my story ..
edit: I was able to restore a old backup of 1.7 carbon ...lol. better than nothing or a TW rom, that's for sure.
When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app
dpeeps74 said:
When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk
cjmcsw87 said:
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
OK, I have one for you to try, use the original rom zip (don't edit the update-script), when you flash in recovery and it failed, select boot and boot back into recovery, then reflash again. Try it with the latest TWRP 2.6.3.2.
SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:
cjmcsw87 said:
SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:
Click to expand...
Click to collapse
Nice, glad you have a happy ending!!
buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
Me too buddy, let me tell ya ..
I appreciate the advice along the way. Thank you.
now I just have to decide if I want carbon or pac as my daily driver for awhile.. Carbon is what i've almost always used after I figured out how bloated and laggy TW is.. Best of all my PagePlus flash is perfectly fine, didn't have to add APN's or mess with anything else to get data to work.
I hope this thread helps somebody else.
I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you
umka83 said:
I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you
Click to expand...
Click to collapse
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.
BadUsername said:
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.
Click to expand...
Click to collapse
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
It's a recovery version problem, so either update your recovery or use an older one until you find something that works.
Problem Solved
umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
After conducting my own research with this same problem I discovered a much simpler method of correcting the issue. When flashing KK roms with older versions of custom recoveries, the recoveries did not have sufficient instructions to to handle some of the file system changes in KK. I tried replacing the updater binaries from multiple ROMs to no avail. After about 24 hours of trial and error I managed to successfully flash Cyanogenmod cm-11-20140709-NIGHTLY-d801 and GAPPs aokp_gapps-kk-20140517 to my LG G2 D801. All that had to be done is to update TWRP from 2.6.3.2 to version 2.7.1. This version of TWRP had the necessary instructions to support a KK version custom ROM.
Good Job
Sent from my SM-G900F using XDA Free mobile app
Fixed
buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
I had same issue, installed newest TWRP. Fixed! Used Odin to install.
I had the same issue as the OP. I was trying to flash a rom from the external SD card. I moved it to the Internal SD and it worked.
J
HI all, I have CM12 installed on my rooted phone and this morning when I switched it on, I got a message saying:
"WARNING: Update Cyanogen recovery is disabled. This may cause issues with updating your device. Please enable Update Cyanogen recovery in developer options"
Now, that option is off because I have my custom recovery TWRP installed on the phone, I'd like to keep that and I don't want to reinstall it after the update, so I believe I should ignore the message, but what I wanted to check with you guys is whether ignoring it will in fact cause any issues as this is the first time ever I've seen this message (this update by the way I think is the first one after installing CM12).
Any idea?
thanks
Disregard the message.
Thanks Heisenberg,
I did that but when the phone restarts trying to install the update, it goes straight into recovery mode (TWRP) and from there I don't think I can install the update, as none of the options seem to allow me to do so, see screenshot http://s23.postimg.org/6d6s7wyq3/IMG_20150625_135453.jpg
All right, I downloaded the zip from here http://cyanogen-ota-bacon.somee.com/ and tried to flash it from TWRP, but I get an error, screenshot here http://s28.postimg.org/zb06wtcpp/OTA_error.jpg, any idea why?
Same here, got an error in TWRP logs that prevented the update to install.
I'd like to avoid reflashing stock recovery only to install the update...
Heres the log: http://s29.postimg.org/njqqqlfc7/Screenshot_2015_06_25_08_49_42.png
Seems something related to outdated "build fingerprint" my device has currently 12.0-YNG1TAS17L
I guess the alternative would be to do it thru Cyanogen Recovery, but let's see what more knowledgeable members have to say as, like you, I don't want to have to reinstall TWRP and SU just for the sake of the update
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Thanks for clarifying that davebugyi, then so be it, I'll do it thru cyanogen recovery and then reflash TWRP and probably SU as well
thanks
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse
duratto said:
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
Click to expand...
Click to collapse
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
thanks! Ah OK I see so that's the whole ROM there as opposed to just an update
davebugyi said:
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
Click to expand...
Click to collapse
Do you mean flashing only this update found at the end of the first post?
YNG1TAS2I3 Radio, etc - Mirror - Same as YNG1TAS0YL
md5 - 6d5db5af6c92b814b9a0ebd18341dd8e
Click to expand...
Click to collapse
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Yes, but if I'm not mistaken, judging from the file size, that's the whole ROM
tsnake said:
Do you mean flashing only this update found at the end of the first post?
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Click to expand...
Click to collapse
The file I quoted is not a whole ROM, it's 31 MB.
AH OK, sorry I thught you referred to the 500mb file
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
I'm having the same issue. Anyone?
Got the same problem. Any idea?
duratto said:
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
Click to expand...
Click to collapse
Bump for a fix?
Juergen1337 said:
Got the same problem. Any idea?
Click to expand...
Click to collapse
The solution seems to be installing the new ROM provided. Related problem here http://forum.xda-developers.com/oneplus-one/help/twrp-cm-android-version-mismatch-t3147658
Hello all,
I want to move from CM12 (Wilsons3q) to the latest MIUI 7 Global Stable. Im having a problem getting my phone recognized through the MiFlash program I originally used to get to CM12. I go into fastboot mode on the phone but the program does not recognize the phone. Ive tried this on 2 different computers. I installed the universal ADB drivers and still nothing. Does anyone know why the phone isnt recognized anymore?
I searched through the previous topics and found no answer to my question. Thanks guys
Solved.
Turns out all I had to do was flash the .zip from MIUI with TWRP recovery
It failed the first time so I did it a second time and it worked great.
Leaving this here for anyone else who may run into the same question/ problem
gotmicah said:
Solved.
Turns out all I had to do was flash the .zip from MIUI with TWRP recovery
It failed the first time so I did it a second time and it worked great.
Leaving this here for anyone else who may run into the same question/ problem
Click to expand...
Click to collapse
you flash the update zip through twrp recovery?
NO! Dont flash the update.zip
Download the global version from miui.
the name of what I flashed was "miui_MI4iGlobal_V7.1.1.0.LXIMICK_15c5da242c_5.0.zip"
gotmicah said:
NO! Dont flash the update.zip
Download the global version from miui.
the name of what I flashed was "miui_MI4iGlobal_V7.1.1.0.LXIMICK_15c5da242c_5.0.zip"
Click to expand...
Click to collapse
i download the miui latest version just rename it into update zip. because want to install in stock recovery. so, mean i can directly flash that zip?
fidows said:
i download the miui latest version just rename it into update zip. because want to install in stock recovery. so, mean i can directly flash that zip?
Click to expand...
Click to collapse
Oh I see. I didn't know you were using stock recovery. Im not sure completely, but im assuming that would be safe.
Edit: on second thought, maybe not. I dont have enough information about your situation, what ROM are you running now? im not sure how the stock recovery interacts with different ROMS
gotmicah said:
Oh I see. I didn't know you were using stock recovery. Im not sure completely, but im assuming that would be safe.
Edit: on second thought, maybe not. I dont have enough information about your situation, what ROM are you running now? im not sure how the stock recovery interacts with different ROMS
Click to expand...
Click to collapse
i mean this. im now in miui7. just to make sure if i flash cm13 then. can i flash the miui7 zip directly from twrp?