Related
The last time I flashed a custom rom to my phone was CyanogenMod-7.1.0-RC1-N1.
I'd really like to get ICS on it, but the process seems just so much more confusing this time around. If anyone give me a breakdown of what I'd need to do, or even if they could just point me in the right direction, I'd be grateful.
i never messed with that as they are always a lil buggy i like sense better ^_^ try asking people in that thread im sure they be happy to help you bro
sorry i couldn't help
Mintyass said:
The last time I flashed a custom rom to my phone was CyanogenMod-7.1.0-RC1-N1.
I'd really like to get ICS on it, but the process seems just so much more confusing this time around. If anyone give me a breakdown of what I'd need to do, or even if they could just point me in the right direction, I'd be grateful.
Click to expand...
Click to collapse
There are at least 3 ICS ROMs with 2 are in the working progress and the other we don't know what is the status of it. Spend some time to read first to gain some knowledge and procedures. They are in the Development section of Nexus One. And, remember, once you have Ice Cream Sandwich you don't want to have Gingerbread
u can flash this miui ics as like anyother roms before
http://forum.xda-developers.com/showthread.php?t=1479348
but for other ics roms u need to partition /system. for that first u need to know abt blackrose.
http://forum.xda-developers.com/showthread.php?t=1270589
Sent from my Nexus One using Tapatalk
The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.
Jaiy said:
The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.
Click to expand...
Click to collapse
Restore apps from GB backup might bring FC. It is better to download them from the Google Play
taodan said:
Restore apps from GB backup might bring FC. It is better to download them from the Google Play
Click to expand...
Click to collapse
While, in theory, you are correct, I restored my GB apps using TB because it is very fast to do so. In practice, they all appear to be working just fine. I believe I have run every one of them to make sure.
But I agree that a better general procedure would be to restore the apps themselves from the Play Store then restore your former app data using TB.
Jaiy said:
The process is actually easier than the process you went through to root your phone and install CM7.
First, download the ICS firmware zip file to your phone's sdcard.
Next, make your backup using TitaniumBackup.
For most ICS firmware, you'll need to repartition your hboot. Google for blackrose-manual_120216.zip, download to your computer, unzip and look for the hboot_brcust-220-10-206.nb0 file. This one is pre-configured with the right partition sizes. Follow the instructions in the README file, which are basically:
Update your recovery firmware, by downloading to your computer and then using fastboot from your computer. I used the Amon-RA recovery for CM and stayed with it for ICS.
On the phone, enable USB Debugging in the CM Developer settings menu.
Boot the phone into the bootloader and go to FastBoot mode. It'll tell you what HBOOT you currently have. Read the instructions in the blackrose README to see which (if any) of the goXX.lol files you need. Then, on the computer:
Code:
fastboot flash recovery goXX.lol
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Next, flash the new hboot:
Code:
fastboot flash hboot hboot_brcust-220-10-206.nb0
The blackrose-manual zip contains fastboot binaries for Linux, Mac and Windows. If you need a fastboot for FreeBSD, send me a PM.
Then boot into recovery, do a Nandroid backup, then a full wipe, then install the ICS firmware zip you put on the sdcard earlier.
That should be all. Once the new system is booted, you'll use Titanium again to restore your apps.
For what it's worth, the BCM firmware is based on CM with all the CM additions you're used to, so things will be pretty familiar. It's running well for me.
Click to expand...
Click to collapse
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?
Mintyass said:
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?
Click to expand...
Click to collapse
The instructions are in the Blackrose thread in the Development section, you don't need to use the manual if you're using Windows.
I would read the blackrose thread so you understand what you are doing and why. Easier to get out of trouble and harder to get into it. You probably did same for CM7. The blackrose hboot is not easy to work with without knowing what you are doing. The backrose thread has pre requisites in OP, like install of drivers if you don't have them.
You guys sure the fastboot command for the exploit has the word "recovery" in it or should be:
fastboot boot go.lol
where go.lol is exact name of exploit from the actual blackrose binary folder depending what version of blackrose you are fastbooting. could be "fastboot boot go2.lol" etc
just a suggestion--
So I was able to use blackrose to repartition my system cache, but now I've got a problem. In the bootloader, when I select "Recovery" the phone hangs on the Nexus "X" logo, and I'm unable to get my phone to reboot into anything but the bootloader.
you probably lost recovery and need to re fastboot it
i once had to fastboot erase system before the recovery would flash
all these issues are in the thread
Would this be the correct thing to do? http://forum.xda-developers.com/wiki/HTC_Nexus_One/Recovery_Images
good info but if you have sdk and know fastboot do this
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it. Usually tools folder.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc
type fastboot devices (to make sure that fastboot "sees" your phone)
type fastboot flash recovery recovery-RA-passion-v2.2.1.img or whatever exact name your recovery is
I was able to get into recovery, but now when I select "Flash zip from sdcard", I get an error saying that there was No Signature and that the Verification Failed.
Mintyass said:
I was able to get into recovery, but now when I select "Flash zip from sdcard", I get an error saying that there was No Signature and that the Verification Failed.
Click to expand...
Click to collapse
You need to disable the signature verification in the recovery and then flash the ROM
Thanks so much for everyone's help! I've got ICS up and running now thanks to you.
Since this forum account is too new to post in the BCM thread, I guess I'll try asking a question here instead.
So far there's two problems I've encountered that would be dealbreakers for BCM. I saw on the BCM thread that voice search is currently broken, but it seems like it's kind of unexpected and will likely be fixed. The other issue I have, that I can't find anyone else complaining about, is that I don't seem to have the Car Home app anymore. Has anybody else run into this issue, or know a fix? I use my phone in my car pretty much every day in my car dock, and make extensive use of both the car home app and the voice search feature for getting navigation directions.
If there's a better place to post these questions, feel free to let me know!
Thanks
audio has been ab issue for me and others on ics and sense roms lately, don't know why. i am back on CM7 Kangs atm bc of it. hope it is found and fixed. the current remedies don't work for me
glad you are up and running, all these roms have issues of some type for a few at least. goes with the territory--
someone should be able to get you a car home apk you can install or push thru adb--i always delete mine as i don't use--sorry. might be able to find it thru search/google
posting here is perfectly fine--it a couple general threads for a "meaningful" post and you will be to ten real quick
enjoy rom
ken
Mintyass said:
This is great! I found blackrose_manual_120216.zip, but the only .nb0 file in it was hboot_blackrose.nb0. Will this work, or do I need to keep looking?
Click to expand...
Click to collapse
Sorry, I wasn't watching this thread over the weekend and I see you have already moved past this. But to answer the question...
I thought the pre-partitioned blackrose-220-10-206 was in that zip, but I see now that I found it on the Evervolv ROM thread in the Nexus One development forum. Sorry for not remembering to mention that.
---------- Post added at 12:08 PM ---------- Previous post was at 11:58 AM ----------
Mintyass said:
Thanks so much for everyone's help! I've got ICS up and running now thanks to you.
Click to expand...
Click to collapse
You're welcome.
So far there's two problems I've encountered that would be dealbreakers for BCM. I saw on the BCM thread that voice search is currently broken, but it seems like it's kind of unexpected and will likely be fixed. The other issue I have, that I can't find anyone else complaining about, is that I don't seem to have the Car Home app anymore. Has anybody else run into this issue, or know a fix? I use my phone in my car pretty much every day in my car dock, and make extensive use of both the car home app and the voice search feature for getting navigation directions.
Click to expand...
Click to collapse
BCM Version RC3.3Ux has very broken voice input. Many folk (including me) have commented that no VoIP apps work with it. Hopefully this will be fixed soon. BCM3.2U2 works fine, so I have reverted to that version for now.
You can install the CarHome app from the Play Store; it doesn't seem to be included in the BCM zip file.
This does work to upgrade from 4.4.2 to 4.4.4 and there was no data/setting loss. I am running Verizon, developer phone, rooted, with xposed. Here are the directions I used:
1. disable Xposed - I just went to the app and uninstalled it
2. boot into bootloader/fastboot - connect your computer to the phone via USB. Then push the down volume and power at the same time. This will take you to the bootloader/fastboot
3. flash stock recovery (fastboot flash recovery yourfilename.img) - to do this (and to flash stock system) you need the motorola fastboot files and you will need to use the command prompt on the PC. for directions and download for the fastboot files check out this link - http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/ To actually download the stock recovery and stock system files you can download them here (look for 4.4.2 verizon - http://sbf.droid-developers.org/phone.php?device=0. I actually pasted the recovery.img/stock.img files into the windows fastboot folder and accessed CMD prompt from there to flash them. I flashed recovery then moved onto stock. I did not reboot until both were done.
4. flash stock system (fastboot flash system yourfilename.img)
5. reboot (stay in the CMD prompt and type - fastboot reboot)
6. update via OTA
7. reboot
You are now stock unrooted 4.4.4, so just re-apply root the same way you did the first time:
1. boot into bootloader/fastboot - you should be able to follow the directions from above to do this now
2. flash custom recovery - you should be able to follow the directions from above to do this now. Note that I tried CWM and it didnt work until I used TWRP. - download the latest version here and stick in the same fastboot folder you were using above - http://teamw.in/project/twrp2
3. boot to recovery - make sure you do this from the bootloader/fastboot screen. To do it, press down until you get to recovery then up to actually select it. I kept pressing power to select which doesnt actually select it.
4. flash SuperSU - this should be on your phone from the first time you rooted. If doing a new root you will need to get it first.
5. reboot
6. re-enable Xposed - i just reinstalled it and all of my settings were back
7. reboot
- BAM you are done!
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
Multiple reports all over the forum say YES. (must flash stock recovery back, FIRST -- OR just use the FXZ and don't worry about having to flash stock recovery...)
Also, to the OP: questions belong in Q&A, not General. See the 2nd Sticky post at the top of the General forum....please post in the correct forums in the future...
I have a vzw DE
I took the 4.4.4 FXZ file from the other thread and just flashed it, no prep, didn't disable xposed.I was flashing in fastboot, not recovery, so its not checking for intact files. Then had to twrp/root and re-enable xposed.
But if you want to take the OTA then your procedure would be good.
Ryphez said:
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
Click to expand...
Click to collapse
There is no difference whatsoever between an unlocked dev edition and any other unlocked X. The ONLY difference is the dev edition keeps its warranty when you unlock.
Whats the best twrp for root on 4.4.4
Mickoou said:
Whats the best twrp for root on 4.4.4
Click to expand...
Click to collapse
How about the latest version from the official source? Here: http://techerrata.com/browse/twrp2/ghost
It will root for you. Just flash w/fastboot, then "fastboot reboot-bootloader", then VOL DOWN to RECOVERY, and VOL UP to select it. When you go to exit, it will offer to install SuperSU Installer. Once booted, launch SuperSU Installer, and select Play Store method.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
No, you should be the guinea pig for all of us.
I can confirm that this works. I did it. I did not lose any data. It took about 20 minutes total. I already had everything installed otherwise you are looking at about 45 minutes.
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
KidJoe said:
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
Click to expand...
Click to collapse
Thanks for the tip. I believe I did it the way I mentioned because last time gravity box didnt have a wifi tether available so I had to modify the system files. this time I didnt touch them.
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
+1 :good:
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
zoid_99 said:
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
Click to expand...
Click to collapse
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Schaweet said:
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thank you Thank you.... That was it.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
1.6 SU was the only issue I had, I got the latest and had no issue
http://download.chainfire.eu/supersu
KidJoe said:
[*]Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Click to expand...
Click to collapse
Where do I get the stock recovery.img file?
Thank you!
fede_arg said:
Where do I get the stock recovery.img file?
Thank you!
Click to expand...
Click to collapse
The OP tells you in the very first post...
To revert completely back to stock
The rootjunkysdl website. http://rootjunkysdl.com/?device=Droid Turbo&folder=Firmware
It's in the firmware section for the Droid Turbo
Download it, unzip it, run the .bat file while in fastboot mode, wait for the magic.
kevinmr82 said:
To revert completely back to stock
The rootjunkysdl website. http://rootjunkysdl.com/?device=Droid Turbo&folder=Firmware
It's in the firmware section for the Droid Turbo
Download it, unzip it, run the .bat file while in fastboot mode, wait for the magic.
Click to expand...
Click to collapse
Thanks, what firmware does this flash? It shows "21.128-15" in the file name so I am just wondering. The latest is 21.44.12.quark_verizon.en.us.
21.21.15 The original firmware from the October, 2014 release
kevinmr82 said:
21.21.15 The original firmware from the October, 2014 release
Click to expand...
Click to collapse
Oh yeah, thanks! I just downloaded it and opened it up. This will flash literally everything from radios to the bootloader to system. Thanks now I have it just in case.
Edit: bootloader stays modified...
where can i find 21.44.12?
Edit: do i flash through rsdlite or mofo?
I have been unable to find that version myself. You don't use RSD or MOFO. After you unzip the file look for the .bat file. Put your phone in recovery mode and open the .bat file. It will flash on its own.
kevinmr82 said:
I have been unable to find that version myself. You don't use RSD or MOFO. After you unzip the file look for the .bat file. Put your phone in recovery mode and open the .bat file. It will flash on its own.
Click to expand...
Click to collapse
Thanks for the reply... I actually messed up my recovery file so I couldnt go that route... luckily it was easy as fastboot flash recovery recovery.img after getting the correct file
Is there any way to get an unrooted system.img to flash with mofo? I'm trying to 'unroot' my phone and keep the modifications I have made, so I can continue using the apps that don't allow me to use them when I'm rooted (Barclays Mobile Banking and Pingit)
That I'm unsure of, have you tried any of the root cloaking apps in the Play Store?
kevinmr82 said:
That I'm unsure of, have you tried any of the root cloaking apps in the Play Store?
Click to expand...
Click to collapse
Yes, they don't work. I tried removing su and superuser.apk, but still no luck. It won't probably work, but I'd like to try, see the differences between a rooted and an unrooted system.img, also see if these apps work on a 'flashed' system.img that is unrooted...
I'll keep trying to convert the system.img_sparsechunk* from the stock rom into a mofo flashable system.img... If I can't do it then I'll open a thread asking for a dd from an unrooted system partition
Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.
do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you
Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/
OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance
Sir
can you capture ota for myphone uno
gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Working internal detect for pc and file ?
marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM
marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.
success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man
Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!
OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.
Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?
OscarBrito said:
Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?
Click to expand...
Click to collapse
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.
KingRoot
prdog1 said:
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.
Click to expand...
Click to collapse
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.
OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
None of the unroot options put things back to 100% stock. They just remove root. The only way to remove all traces is to fastboot flash the system.img
If you're going to run rooted, forget about OTA and learn about fastboot.
General > sticky roll-up > adb and fastboot
Reset
prdog1 said:
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.
Click to expand...
Click to collapse
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.
OscarBrito said:
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.
Click to expand...
Click to collapse
Nope. Have to flash stock image as posted above.
prdog1 said:
Nope. Have to flash stock image as posted above.
Click to expand...
Click to collapse
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.
OscarBrito said:
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.
Click to expand...
Click to collapse
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img
danarama said:
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img
Click to expand...
Click to collapse
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
Fastboot works with Linux also.
OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.
danarama said:
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.
Click to expand...
Click to collapse
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Better chance of bricking it with ToolKit than with manual fastboot. I run stock rooted with TWRP also. Takes 2-3 minutes to update with fastboot. If toolkit fails will most likely need fastboot to fix it anyway.
OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.
danarama said:
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.
Click to expand...
Click to collapse
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.
OscarBrito said:
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.
Click to expand...
Click to collapse
I can't see how any Linux user would be afraid of terminals
Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...
imor said:
Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...
Click to expand...
Click to collapse
You will lose root. Flash supersu from recovery before first boot
Ok, just confirming here before I mess up. I have an international N6 rooted with stock recovery running LMY47Z. I can't update OTA. So I should flash the full stock image and then run cf-auto-root before rebooting.
Is this correct? Will I lose my user data when I do this? If so, what's the easiest way to backup and restore? Can't I flash the 25MB update .zip instead?
Thanks!