Related
Hi there,
A while ago I got a OnePlus One which came with ColorOS loaded. I of course googled my way to get the Cyanogenmod and followed these instructions.
http://www.youtube.com/watch?v=QDKOEtN9pbo
I'm currently on the 25R firmware and I know there are some updates after that but the phone doesnt detect any update release. I would like to know why the OTA updates are not being picked up from the phone. Was it simply the easy method mentioned above?
I also thought of reflashing it properly and found some instructions on the web.
Code:
Install Android tools (and drivers if you use Windows-crap). You need the fastboot and adb tools
Get http://dist01.slc.cy...ed-fastboot.zip and unpack it
Enable USB debugging on the phone
Run adb reboot-bootloader
Once bootloader started run: fastboot oem unlock
After automatic reboot, do steps 3 & 4 again
In the directory where you unpacked it, run in a console
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img (or userdata.img for 16G version)
fastboot oem lock
fastboot reboot
These instructions will somehow get the OTA updates working, am I right to assume that this method would rewrite everything and I would lose the recovery software of the ColorOS? Also are the Android tools these?
http://developer.android.com/sdk/index.html
Fastboot and ADB, I can use this one right?
http://forum.xda-developers.com/showthread.php?t=2588979
I appreciate the help and a few explanations.
Cheers.
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
dude777 said:
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
Click to expand...
Click to collapse
If you're looking for a completely fresh install, just go to my guide thread (link in signature) and follow section 8.
Transmitted via Bacon
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood.
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Look on YouTube on how to use this toolbox and it will completely wipe your phone then flash clean.
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
A toolbox is completely unnecessary, and they're more trouble than they're worth. Plus, nobody learns anything even using a toolbox, and that knowledge is crucial for when things go wrong.
Transmitted via Bacon
DON'T use a toolbox please
Learn as you go by doing things properly, I speak from my own experience. These skills and knowledge that you gain will help if you ever run into any issues
Go here to install the adb drivers computer wide so you can flash from any folder on your computer, it makes your life so much easier
http://forum.xda-developers.com/showthread.php?t=2588979
Then follow timmaaa guide on how to start fresh with a complete 44s ROM
Sent from my A0001 using XDA Free mobile app
Thanks guys for the effort here, really like your guides timmaaa very clear and non confusing. Yes I would like to avoid shortcuts as I took the easy route and now the phone goes in hiatus moment when calling. I'll get around this in the weekend and see how that goes.
Cheers.
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
dude777 said:
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
Click to expand...
Click to collapse
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
timmaaa said:
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
Click to expand...
Click to collapse
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
dude777 said:
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
Click to expand...
Click to collapse
You do indeed restore a nandroid backup with the recovery that you made the backup with. And yes it is saved on the phone so you will need to transfer it to your PC. You're not being a pain in the butt, you're doing the right thing and researching before attempting something.
Transmitted via Bacon
Yeah I agree users like you that research crap before attempting something are much preferred over users that blindly use a toolbox then come complaining cuz they messed something up but dunno how to fix it. I always do my research before flashing just like you are doing. Just make sure you install the drivers I linked to computer wide on your windows computer and you should have no problems, no need to install separate SDK for android and copy the files you're flashing into a special folder, etc
info update
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
If you follow timmaaa's guide you should be good to go. I'm a noob myself and just did it over the weekend and its a blast. Good luck
Cheers
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
Lol really? Did u completely ignore reading the thread that you just posted in??
[emoji15] [emoji58]
My question is this: I want to take an adb backup, then unlock my bootloader, then restore the adb backup. Will it work (and not brick my device like I've done before!), and if so, will my bootloader still be unlocked or will it be locked again ?
Thanks for advice. If it's really necessary I know I can lose my data and restore everything, but it's a time-wasting pain so I thought I'd try it this way!
Currently I'm on 05Q official stock, no root/busybox, stock recovery and kernel. I.e. everything stock.
pmedwards25 said:
My question is this: I want to take an adb backup, then unlock my bootloader, then restore the adb backup. Will it work (and not brick my device like I've done before!), and if so, will my bootloader still be unlocked or will it be locked again ?
Thanks for advice. If it's really necessary I know I can lose my data and restore everything, but it's a time-wasting pain so I thought I'd try it this way!
Currently I'm on 05Q official stock, no root/busybox, stock recovery and kernel. I.e. everything stock.
Click to expand...
Click to collapse
What about
fastboot boot (twrp) recovery.img
And then make a backup in recovery
And copy the backup somewhere safe
I'm not sure if that works on 5Q though
waterdaan said:
What about
fastboot boot (twrp) recovery.img
And then make a backup in recovery
And copy the backup somewhere safe
I'm not sure if that works on 5Q though
Click to expand...
Click to collapse
Isn't that the same as adb backup?
pmedwards25 said:
Isn't that the same as adb backup?
Click to expand...
Click to collapse
A backup in recovery backs up
System
Data
It won't backup your sdcard
I don't know what adb backup does, I think it backs up your apps and data
waterdaan said:
A backup in recovery backs up
System
Data
It won't backup your sdcard
I don't know what adb backup does, I think it backs up your apps and data
Click to expand...
Click to collapse
You can add parameters to make it backup system, apks, app data, sdcard and others. Should this work in theory?
waterdaan said:
What about
fastboot boot (twrp) recovery.img
And then make a backup in recovery
And copy the backup somewhere safe
I'm not sure if that works on 5Q though
Click to expand...
Click to collapse
You can't boot a recovery with a locked bootloader anymore, they patched that way back in the 30O update I believe.
Transmitted via Bacon
I have not rooted my phone yet and previously come from using nexus devices.
I'm on stock lollipop rom and was wondering how I should proceed.
step one would be backing up the TA partition.
following that, unlock the bootloader. After that I was wondering if I need to downgrade to kitkat to continue or if I could flash a kernel with twrp and try to get into twrp, wipe everything and flash cm12.1 + gapps + supersu and proceed from there.
My question is, do I need to downgrade to kitkat stock to proceed or is there a way for me to gain recovery and flash a rom without downgrading?
you will need to downgrade to KK to get root access then install a stock rom that had been pre-rooted for lollipop, you don't have to unlock the bootloader but if you do then you can use a kernel that has recovery built in
Richy99 said:
you will need to downgrade to KK to get root access then install a stock rom that had been pre-rooted for lollipop, you don't have to unlock the bootloader but if you do then you can use a kernel that has recovery built in
Click to expand...
Click to collapse
But to flash a rom one does not need root, just recovery, or am I wrong there? Wouldn't it be possible to flash a kernel using fastboot just to gain access to twrp (I know that would cripple the stock rom), and then wipe everything and then just go ahead and flash cm12.1 using a microsd card?
I might be totally wrong. If there is not other way I guess I need to downgrade.
Oh and my end goal is to flash cm12.1.
Arju007 said:
But to flash a rom one does not need root, just recovery, or am I wrong there? Wouldn't it be possible to flash a kernel using fastboot just to gain access to twrp (I know that would cripple the stock rom), and then wipe everything and then just go ahead and flash cm12.1 using a microsd card?
I might be totally wrong. If there is not other way I guess I need to downgrade.
Oh and my end goal is to flash cm12.1.
Click to expand...
Click to collapse
But you cannot flash a kernel with a locked bootloader, and you cannot backup the TA without root...
So, you need to root before unlocking the bootloader.
So, downgrade to KK FW .93, root, backup TA partition (If you are going to unlock the boot, otherwise there is no point), install recovery, flash a pre-rooted lollipop rom.
No need for unlocking the boot at all unless you want a custom kernel
But if you want CM12,
downgrade to KK FW .93, root, backup TA, unlock boot, install a recovery of your choice either by a LB way (e.g. dual recovery) or by fastboot a boot.img, flash CM12.1
gregbradley said:
But you cannot flash a kernel with a locked bootloader, and you cannot backup the TA without root...
So, you need to root before unlocking the bootloader.
So, downgrade to KK FW .93, root, backup TA partition (If you are going to unlock the boot, otherwise there is no point), install recovery, flash a pre-rooted lollipop rom.
No need for unlocking the boot at all unless you want a custom kernel
But if you want CM12,
downgrade to KK FW .93, root, backup TA, unlock boot, install a recovery of your choice either by a LB way (e.g. dual recovery) or by fastboot a boot.img, flash CM12.1
Click to expand...
Click to collapse
Ah I see, root is needed to backup TA partition.
I know my bootloader needs to be unlocked as I flash Cyanogenmod 12.1 on it. I fell more secure using fastboot soo I'll probably go that way.
So to downgrade, do I use flashtool and find a kk fw .93 ftf file to flash? If I understand correct, this can be done without unlooking the bootloader.
Then from there I'll have to root with looked bootloader, backup TA partition and then unlock bootloader, and then flash kernel with twrp and then proceed to flash cm12.1 or anyother custom rom.
(Sorry If my question is a mess).
Arju007 said:
Ah I see, root is needed to backup TA partition.
I know my bootloader needs to be unlocked as I flash Cyanogenmod 12.1 on it. I fell more secure using fastboot soo I'll probably go that way.
So to downgrade, do I use flashtool and find a kk fw .93 ftf file to flash? If I understand correct, this can be done without unlooking the bootloader.
Then from there I'll have to root with looked bootloader, backup TA partition and then unlock bootloader, and then flash kernel with twrp and then proceed to flash cm12.1 or anyother custom rom.
(Sorry If my question is a mess).
Click to expand...
Click to collapse
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
gregbradley said:
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
Click to expand...
Click to collapse
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
There are plenty of reasons to flash it, only one of them is if it is stable....
gregbradley said:
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
Click to expand...
Click to collapse
Thank you! Makes much more sense now.
ondrejvaroscak said:
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Well there are unofficial builds with fixes from members who has the Leo build. The official one does not have all fixes as of yet. There are cm12.1 unofficial builds out now. Being able to test out the latest and greatest is the beauty of it.
gregbradley said:
There are plenty of reasons to flash it, only one of them is if it is stable....
Click to expand...
Click to collapse
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
For some its a first step into something new, it is always a learning curve. Some just like to have the "latest" version.
ondrejvaroscak said:
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Coming from a different device does not mean that one does lack basic knowledge. I previously used lg g2 and prior to that I used nexus 5, nexus 4 and older devices. All could be managed using fastboot. Those phones does not have drm keys that needs to be backed up. Hence I did not need that knowledge.
Either way, thank you for enlightning me. I felt to ask here in Q&A section rather than being sorry about not asking.
Arju007 said:
Coming from a different device does not mean that one does lack basic knowledge. I previously used lg g2 and prior to that I used nexus 5, nexus 4 and older devices. All could be managed using fastboot. Those phones does not have drm keys that needs to be backed up. Hence I did not need that knowledge.
Either way, thank you for enlightning me. I felt to ask here in Q&A section rather than being sorry about not asking.
Click to expand...
Click to collapse
OK. Sorry for being a bit too sceptical. Sometimes it is frustrating here with all the same questions and stories of ignorance seems not your case.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
OK. Sorry for being a bit too sceptical. Sometimes it is frustrating here with all the same questions and stories of ignorance seems not your case.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
That's fine, I totally understand you! Hope to be pro xperia user soon haha :silly:
@gregbradley Had a noob moment here and now I'm stuck. I tagged you incase you would know how to help me.
So I downgraded to .93 kitkat. All worked well.
Then I managed to root it using giefroot. All worked well.
Then I installed xzdualrecovery. It booted into twrp, I wiped everything beside internal storage and tried to flash cm12.1. I received an error.
I forgot to unlock the bootloader (ofcourse).. which is the mistake I did.
So now I'm stuck. When I turn on the phone the sony bootsplash screen comes on and it does not go past that, due to my device not having a rom.
I tried holding down the volume key and plugging in the device to my computer. My computer does not recognize what device it is but it does make a notification sound saying that I have connected a device to my computer. Fastboot doesn't work on lockedbootloader as far as I know. The flashtool recognizes the device as a flash device for around a minute when connected to the computer using volume down. After a minute my device just turns off and on leaving flash mode. So that's the current status.
Do you or anyone else have any suggestions to how I can revive my phone?
and yes I know, I feel like a noob!
Never mind, I gave it another go with flashtool and managed to get it boot!
and yes, I feel like a pro!
Don't forget to backup the ta patition before unlocking the bootloader.
Also no need to wipe system when flashing
gregbradley said:
Don't forget to backup the ta patition before unlocking the bootloader.
Also no need to wipe system when flashing
Click to expand...
Click to collapse
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
Use NDRUtils app to boot to a different recovery
Or just press volume up when the phone vibrates twice when you are booting it to get to CMW
Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
/edited
i would wipe really everything despite usb otg and external sd card in advanced wipe of twrp before succeeding.
tell me if that works for you
um, i read you already had that issue again even after unlocked bootloader, try flashing a rooted lollipop .zip in recovery.
and then try wiping and flashing cm12.1 again if a full wipe (also sdcard) doesn't work
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
well, as you wrote me in pm you did mount "system", just do nothing in the mount menu after entering recovery. i also never did that.
Is it possible my phone to hard brick or soft brick itself while i use it with a custom rom? I got this phone 3 weeks ago and if i break it, no smartphone for me for years (very tight budget).
geniiii said:
Is it possible my phone to hard brick or soft brick itself while i use it with a custom rom? I got this phone 3 weeks ago and if i break it, no smartphone for me for years (very tight budget).
Click to expand...
Click to collapse
Most cases a custom recovery for your phone will not do any harm
But before flashing read posts carefully because I soft bricked my phone because of a buggy twrp build
sjandroiddeveloper said:
Most cases a custom recovery for your phone will not do any harm
But before flashing read posts carefully because I soft bricked my phone because of a buggy twrp build
Click to expand...
Click to collapse
I meant a custom rom, i want to use FlexOS but i am kinda worried that it could brick my device while i use it. Is that possible?
I am already using a custom recovery, supersu and xposed alpha 3.
geniiii said:
I meant a custom rom, i want to use FlexOS but i am kinda worried that it could brick my device while i use it. Is that possible?
I am already using a custom recovery, supersu and xposed alpha 3.
Click to expand...
Click to collapse
No it will not brick
But you must first have enough info of what you are doing
sjandroiddeveloper said:
No it will not brick
But you must first have enough info of what you are doing
Click to expand...
Click to collapse
Thanks!
Sorry to hijack, but it's kind of related. Are there consequences to flashing the incorrect regional stock ROM?
Blkdrgn415 said:
Sorry to hijack, but it's kind of related. Are there consequences to flashing the incorrect regional stock ROM?
Click to expand...
Click to collapse
No just keep in mind the model like xt1033 or xt1032
sjandroiddeveloper said:
No just keep in mind the model like xt1033 or xt1032
Click to expand...
Click to collapse
Just to be clear, mines is a XT1039 with a CID of 7. My build number is also ""KXB21.14-L1.56" which is exactly matches with Germany where as every other one with CID7 ends with "-1", can I also use the other regions or do I need to use Germany. What are also the differences between the regions?
Blkdrgn415 said:
Just to be clear, mines is a XT1039 with a CID of 7. My build number is also ""KXB21.14-L1.56" which is exactly matches with Germany where as every other one with CID7 ends with "-1", can I also use the other regions or do I need to use Germany. What are also the differences between the regions?
Click to expand...
Click to collapse
The basic thing is you can flash different region firmwares for the same specific device like xt0139 in you case as I was able to flash both Asian and Brazilian firmware in my xt1033
The difference in the firmwares in region specific apps and different radios
sjandroiddeveloper said:
The basic thing is you can flash different region firmwares for the same specific device like xt0139 in you case as I was able to flash both Asian and Brazilian firmware in my xt1033
The difference in the firmwares in region specific apps and different radios
Click to expand...
Click to collapse
Thanks for the help, one last thing though. What if I made a recovery via CWM to my internal SD, but moved it to my external SD, would the recovery still work, and are there any risks of flashing a recovery that is incomplete as whenever I use Recovery Manager to backup to my external SD, it always hangs at "Generating md5 sum" and I'm forced to manually restart.
Blkdrgn415 said:
Thanks for the help, one last thing though. What if I made a recovery via CWM to my internal SD, but moved it to my external SD, would the recovery still work, and are there any risks of flashing a recovery that is incomplete as whenever I use Recovery Manager to backup to my external SD, it always hangs at "Generating md5 sum" and I'm forced to manually restart.
Click to expand...
Click to collapse
By recovery do you mean backup
And press thanks instead of saying
sjandroiddeveloper said:
By recovery do you mean backup
And press thanks instead of saying
Click to expand...
Click to collapse
I think so. Whatever CWM calls it's backups.
Blkdrgn415 said:
I think so. Whatever CWM calls it's backups.
Click to expand...
Click to collapse
Recovery means the software that can perform tasks like flashing wiping or backing up
And its always called backups and not recovery be it cwm or twrp
Blkdrgn415 said:
Thanks for the help, one last thing though. What if I made a recovery via CWM to my internal SD, but moved it to my external SD, would the recovery still work, and are there any risks of flashing a recovery that is incomplete as whenever I use Recovery Manager to backup to my external SD, it always hangs at "Generating md5 sum" and I'm forced to manually restart.
Click to expand...
Click to collapse
Yes you can made backup in internal memory and move it to external memory or even to other storage devices or to your computer. If you want to restore the backup again, put the backup in concerned folder in your mobile and restore it from recovery :good:
sjandroiddeveloper said:
Recovery means the software that can perform tasks like flashing wiping or backing up
And its always called backups and not recovery be it cwm or twrp
Click to expand...
Click to collapse
Mr Y said:
Yes you can made backup in internal memory and move it to external memory or even to other storage devices or to your computer. If you want to restore the backup again, put the backup in concerned folder in your mobile and restore it from recovery :good:
Click to expand...
Click to collapse
So is there any threat to restoring a backup that may be corrupted or incomplete since I manually restarted when it hung up at "Generating md5 sum..."?
Also, will using these files completely restore my phone back to when I first got it? For example, if a crucial system file was corrupted, would using these files fix it, or if my phone has been soft bricked, would it fix it?
http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
+thanks
Blkdrgn415 said:
So is there any threat to restoring a backup that may be corrupted or incomplete since I manually restarted when it hung up at "Generating md5 sum..."?
Also, will using these files completely restore my phone back to when I first got it? For example, if a crucial system file was corrupted, would using these files fix it, or if my phone has been soft bricked, would it fix it?
http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619
+thanks
Click to expand...
Click to collapse
1. If the backup you made previously was corrupted or incomplete, then the recovery wont start the process of restoring.
2. Yes. It will fix the soft-bricks and the phone will be restored to its "Out of box" state except your bootloader will still be in unlocked state since there is no syntax to lock your bootloader in the given link.
Mr Y said:
1. If the backup you made previously was corrupted or incomplete, then the recovery wont start the process of restoring.
2. Yes. It will fix the soft-bricks and the phone will be restored to its "Out of box" state except your bootloader will still be in unlocked state since there is no syntax to lock your bootloader in the given link.
Click to expand...
Click to collapse
Thank you so much, I've been contemplating whether to use my recovery and the stock firmware for weeks.
+thanks
Blkdrgn415 said:
Thank you so much, I've been contemplating whether to use my recovery and the stock firmware for weeks.
+thanks
Click to expand...
Click to collapse
I'll advise you to keep stock firmware as safety measurements (if something goes wrong) and explore other ROMs and tweaks.:good:
Mr Y said:
I'll advise you to keep stock firmware as safety measurements (if something goes wrong) and explore other ROMs and tweaks.:good:
Click to expand...
Click to collapse
Will do, I'm new to phones in general, do you have any recommendations on popular ROMs for my Moto G 4G/LTE XT1039 KitKat 4.4.4?
Official CM 11 are stable in my opinion. Resurrection Remix ROMs also doig great job. BTW im CM fanboy. So better test yourself to choose wisely.
I am new to rooting, and decided to root my Galaxy Note II SGH-i317m a few days ago. I used a method with no adb access...i think. Here's the reference thread, just in case I'm wrong: http://forum.xda-developers.com/showthread.php?t=1980644
I got a bit overenthusiastic, and got TWRP while forgetting to unlock my bootloader first. Now, my phone will only boot into TWRP. All 4 reboot options go back to TWRP. What is the best way to get my phone back to working? I understand that I may have to lose my data. It doesn't matter: my top priority is getting my phone to work again.
Thanks in advance!
EDIT: I'm sorry if this is in the wrong place. I'm new here.
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
EMONESSboy said:
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I just tried that, and no change. Just to clarify, the only thing I can boot into at the moment is recovery mode.
I think what I need to do is flash the stock recovery back onto my phone. Is this a possible solution? If so, how should I go about doing it? I currently cannot access download mode.
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
I Can Help
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
[email protected] said:
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
Click to expand...
Click to collapse
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Phoenix204 said:
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Click to expand...
Click to collapse
tried system restore with twrp?
try it first and if ur not sure that it will work just make backup of boot , efs , system and data(if necessary) via twrp to sd card copy the backup to pc via card reader or something and extract the system backup there should be a file named build.prop in system folder edit it and do it like this :
under #additional build properties
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.root_access=1
find the above lines and edit the parameters as i have shown to you use notepad++ to edit the file save it the last line will give ya root access by default and second last will make it debuggable just save it repack and flash with twrp cheers
hit thanks
Alright. Since I can't find another thread like this one, I will assume that I am one of the first to have this problem. Here is what I did.
I used samsung-firmware.org to find the latest firmware for my phone, which includes both ROM and recovery. Other brands probably also have a website like this.
I used Odin to flash the firmware onto my phone - this wiped my data, but removed TWRP, which is an acceptable solution to me. I might also have wiped my data while playing around with TWRP trying to fix my phone - I'm not sure.
Thanks to both EMONESSboy and [email protected] for their help. I ended up going with something similar to EMONESSboy's solution, since the commands seemed a little risky. Thanks anyways, your help is much appreciated!
IRIS Fuel50
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
mzn.facebook said:
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
Click to expand...
Click to collapse
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Kingaroot
Phoenix204 said:
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Click to expand...
Click to collapse
Actually, what happend was that i tried to root my phone through Kingaroot. It shows some error at 90%. After few seconds my phone gets rebooted and snce then, it is showing Mfr LOGO only.
I have tried Factory reset, wipe cache partition etc.
I had lollipop earlier on my phone.