Related
Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.
tclayson said:
Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.
Click to expand...
Click to collapse
GOT recovery? You have a Milestone then? You are on the wrong path then. Clockwork Recovery Mod doesn't work on the Milestone, nor does ROM Manager.
You need to reflash the stock sbf for your country, then flash the rootable sbf, place OpenRecovery on your SD Card, and root the phone, flash a custom ROM and reboot. Look at the tutorials in the Milestone development forum and ask here if you have any other questions.
I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks
tclayson said:
I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks
Click to expand...
Click to collapse
It doesn't work, even though it shows it as supported. Because the bootloader is not unlocked on the Milestone, it will cause a soft brick. You will need to follow my instructions to get your Milestone running on MIUI again. The OTA update for MIUI works for devices with CWM installed, so it doesn't really work with Milestone. You'll need to manually update MIUI when DannyDroid posts the updates.
Ah gutted, ok thank you for that. I will follow your instructions. Thanks for clearing it up for me.
Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?
tclayson said:
Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?
Click to expand...
Click to collapse
People say that ROM Manager MIGHT work on Milestone. I don't think so and I wouldn't risk it just for OTA updates, seeing as the miuiAndroid build is very basic compared to the one Danny releases. Better to just wait for his releases, a lot more worthwhile!
Ok, well thank you very much! Restored to stock and gonna keep on top of danny's releases. Thanks skadude.
DJ Steve ported CWM 4.0.1.4 with the release of 507.
Requirements:
Stock 5xx based rom [Honeystreak is not supported!]
Ability to enter fastboot mode: Fastboot+ADB.zip
Battery with 60% or greater charge
Basic understanding of the command line
Install Instructions:
Download recovery.img
flash the recovery with "fastboot flash recovery recovery.img"
Finished
Credits:
DJ_Steve for porting it
Koush for creating clockwork mod
I take no credit beyond this basic guide
Notice:
The Streak 7 with HC might now detect the driver properly, if it doesnt you must force install it using the "Android ADB Interface" from the list of available drivers
Will not work on 2.2.x, you must use CWM 3.0 for that.
Do not attempt to wipe data from within CWM, it will likely case a boot loop afterwards.
Thank you!!
Can I just push this recovery to my recovery partition within 3.2?
Im having issues having my PC at work recognize the fastboot device, and installing the drivers.
I am on xp..
TIA!
'error: cannot load 'recovery.img'
I got fastboot going fine, commands like 'fastboot reboot' are working.
However just above when I use your line to flash recovery, any ideas on what it might be!?
Uploaded new version of fastboot+adb.zip hopefully it has the correct IDs so you dont have to force install it.
Are you sure you downloaded the image correctly, and did you name it correctly when using fastboot
Yeah I was making a repeated typo when pointing fastboot to the recovery but its all working now, thanks a lot.
Clockwork mod (cool blue writing) and rooted all within a few days, good work and thanks to all involved.
FWIW I tried this on the T-MO stock 2.2.2 ROM. The install went fine, I copied S7-4.0.1.4.img to recovery.img and ran the fastboot command with no problems.
I power up the Dell Streak 7 while holding power and the up volume key, and get the menu as expected. I Select "Software Upgrade via update.pkg on SD Card", and the message "Booting recovery kernel image" is displayed.
At this point the machine seems to be frozen. I can reset with a paper clip, and reboot the machine into 2.2.2 just fine, but if I cannot resolve why it does not show the clockwordmod menu, then I guess it is back to NVFLASH.
So what am I doing wrong? do I need an SD card in the device with an update.pkg on the card? Or is there something else?
Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.
TheManii said:
Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.
Click to expand...
Click to collapse
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?
Post updated, i needed someone to actually confirm that it didnt work as i dont have access to a s7
dblml320 said:
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?
Click to expand...
Click to collapse
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.
"waiting for device " and nothing happen !!! what should i do? i can not install driver using files in : Fastboot+ADB\Win32\Streak 5+Streak 7+Venue\Win7 !
cdzo72 said:
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.
Click to expand...
Click to collapse
Like he said if you flashed it on a s7 that's still on 2.2.x just reflash with the CWM 3.0 one and that one will work fine on 2.2.x
Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"
Not the stock one, as no other rooting tools work on it.
Ways to get around it include: using a pre-rooted rom or using a custom rom (which are normally pre-rooted)
Something may be wrong with your device/install if that is coming up. Or possibly your download was bad, try re-downloading it.
I tried re-downloading didn't work, I have stock rom, I don't think I can install a custom or pre-rooted rom without installing CWM?
You can with nvflash, as honeystreak is ment to be installed with nvflash then updated with the bundled CWM, which is prerooted
Whichever method you decide is up to you, as I cannot formally recommend that one method is better then the other.
thesmacker11 said:
Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"
Click to expand...
Click to collapse
Well just as an update I tried this on a windows xp, windows 7 32bit, windows 7 64bit computer, and redownloaded that file each time and it still does the same thing on my device.
It's likely your device itself that's the issue then, I cant be more specific as I dont own a S7
I'm not sure if I should be asking questions here or over in another forum. Figure I'll start here...
I was sorely missing app2sd in honeycomb so went to use and install Link2SD figuring I'd use that. But it doesn't seem to see the second partition I've made on my SDHC card. I can mount the card on Mac OS and Linux and both mount the two partitions on the card so I feel pretty sure I formatted the card correctly. I saw some comment about a change in the way CW mounts things and it causing troubles in the Link2SD thread but I don't understand enough about the magic of Android and how it mounts discs, although I know it had Linux roots, so the comments in that thread weren't clear to me what I can do to get Link2SD working or for that matter even start to gather info to try to figure out what's wrong. Can anyone help me out or point me to a thread that can get me started in figuring out what's going wrong?
Sent from my HTC Flyer P512 using Tapatalk
ok so i installed the drivers for fastboot and i can enter fast boot , but how can i push the file? soory im a newb with the streak.
The problem
I have a rooted Xperia T, unlocked bootloader, and now I would like to flash a CM rom (10.1.3 stable). I have attempted to use some tutorials to simply boot into recovery using GooManager (flashing TWRP) or ROM Manager (flashing CWMR), but neither of these seem to work - when I attempt to boot into recovery, my phone simply reboots normally.
I then have tried to flash CWMR from my computer (I have a mac), and I can do fine until I reach a message in terminal detailing a failure that I can't seem to find elsewhere on the internet. (See screenshot)
So, I have hit a dead end - can't flash recovery on device, can't flash recovery via desktop.
Screenshots
View attachment 2703144 View attachment 2703145 (Click to enlarge)
Details
USB debugging is enabled
When I am in fastboot the LED is blue (correct fastboot, I rooted my phone)
I have downloaded the CM .zip, the necessary gapps, and have backed up my apps 'n data with TB and simply copying files
I renamed the recovery on my desktop from 15102012.img (as I downloaded it) to cwmrecovery.img for ease of use
What is the problem on my device and on terminal?
What can I do to fix either?
Is there a step I have missed?
Have I missed a really obvious detail (if so, I feel really bad...)
If you need anything else to help me, just let me know.
Thanks guys.
Gepru said:
The problem
I have a rooted Xperia T, unlocked bootloader, and now I would like to flash a CM rom (10.1.3 stable). I have attempted to use some tutorials to simply boot into recovery using GooManager (flashing TWRP) or ROM Manager (flashing CWMR), but neither of these seem to work - when I attempt to boot into recovery, my phone simply reboots normally.
I then have tried to flash CWMR from my computer (I have a mac), and I can do fine until I reach a message in terminal detailing a failure that I can't seem to find elsewhere on the internet. (See screenshot)
So, I have hit a dead end - can't flash recovery on device, can't flash recovery via desktop.
Screenshots
View attachment 2703144 View attachment 2703145 (Click to enlarge)
Details
USB debugging is enabled
When I am in fastboot the LED is blue (correct fastboot, I rooted my phone)
I have downloaded the CM .zip, the necessary gapps, and have backed up my apps 'n data with TB and simply copying files
I renamed the recovery on my desktop from 15102012.img (as I downloaded it) to cwmrecovery.img for ease of use
What is the problem on my device and on terminal?
What can I do to fix either?
Is there a step I have missed?
Have I missed a really obvious detail (if so, I feel really bad...)
If you need anything else to help me, just let me know.
Thanks guys.
Click to expand...
Click to collapse
I would say, try to do it on a native Windows 7 pc. No VMware or something. That's the most safe/relieable option you have.
Alright, I returned to the problem and found a solution:
I installed TWRP via Flashtool for mac, and from there it all went swimmingly. The fact that I forgot to put the CM ROM on my phone was a little stupid, but that too worked out in the end.
Typed happily on my CM 10.2.0 Xperia T
What CM 12 ROM you used?
Gepru said:
Alright, I returned to the problem and found a solution:
I installed TWRP via Flashtool for mac, and from there it all went swimmingly. The fact that I forgot to put the CM ROM on my phone was a little stupid, but that too worked out in the end.
Typed happily on my CM 10.2.0 Xperia T
Click to expand...
Click to collapse
I am using 10.2.0, mint.
Not 12
Ops...
Just a thing: on CM 10.2, have you got problems with microphone? I've used CM starting from last release (11) and I've always found that mic gain is too high. This cause that every record I do is too overdriven.
Can you test it, recording a vocal track very close to mic? I've always liked AOSP based ROM, but this issue made me came back to stock ROM.
Thanks in advance for the reply!
Gepru said:
I am using 10.2.0, mint.
Not 12
Click to expand...
Click to collapse
Hello all,
I rooted my Xperia SP and had installed the Cyanogenmod 11 (last stable-ish release, milestone or something) successfully.
After being encouraged by a co-worker that the nightly builds are pretty safe too, I installed a 12.1 nightly (can't remember which, though).
After that I couldn't reboot to bootloader any more to back up my phone.
I can select it in the reboot menu, but the phone will just cycle into a normal reboot and start Cyanogen.
Being brave I installed another nightly (current version: 12.1-20151010-NIGHTLY-huashan), hoping that would help.
It didn't, but luckily that version works, too.
Otherwise the phone works well, but I would like to be able to reboot into the bootloader to create a system backup, before I install more nightlies.
Rebooting into recovery works. However, have no backup option there.
To clarify: booting into bootloader is not necessarily what I want, it's the backup option that I'm after.
On the other hand, this not working properly is kind of a red flag, so I want to make sure nothing is going sideways...
Any advice would be much appreciated!
Thanks!
Merlin
centaury02 said:
Hello all,
I rooted my Xperia SP and had installed the Cyanogenmod 11 (last stable-ish release, milestone or something) successfully.
After being encouraged by a co-worker that the nightly builds are pretty safe too, I installed a 12.1 nightly (can't remember which, though).
After that I couldn't reboot to bootloader any more to back up my phone.
I can select it in the reboot menu, but the phone will just cycle into a normal reboot and start Cyanogen.
Being brave I installed another nightly (current version: 12.1-20151010-NIGHTLY-huashan), hoping that would help.
It didn't, but luckily that version works, too.
Otherwise the phone works well, but I would like to be able to reboot into the bootloader to create a system backup, before I install more nightlies.
Rebooting into recovery works. However, have no backup option there.
To clarify: booting into bootloader is not necessarily what I want, it's the backup option that I'm after.
On the other hand, this not working properly is kind of a red flag, so I want to make sure nothing is going sideways...
Any advice would be much appreciated!
Thanks!
Merlin
Click to expand...
Click to collapse
I guess you're confusing recovery with bootloader,
The default recovery CM12.1 and other CM based ROMs come with is "Cyanogen Recovery" which is not very popular coz it lacks many features.
Anyways, TWRP is a pretty good recovery that allows you to backup, restore, etc, and it even has it's own file manager. Download the latest recovery from here and flash it via CM recovery, it will replace CM recovery with TWRP.
Zenith said:
I guess you're confusing recovery with bootloader,
...
Download the latest recovery from here and flash it via CM recovery, it will replace CM recovery with TWRP.
Click to expand...
Click to collapse
Hi Zenith,
thanks for your quick reply! I'll give it a shot and report here if it worked.
I don't think I confuse the two, though.
When I choose reboot, I get to select (amongst the usual) "Bootloader" or "Recovery".
"Recovery" gives me a menu (after reboot) where I could theoretically roll back to a previous backup for example.
"Bootloader" earlier gave me a text-based menu, where I could back my system up, now I can't reach this any more. The phone simply boots Cyanogenmod again.
Anyway, thanks and I'll try out TWRP!
centaury02 said:
Hi Zenith,
thanks for your quick reply! I'll give it a shot and report here if it worked.
I don't think I confuse the two, though.
When I choose reboot, I get to select (amongst the usual) "Bootloader" or "Recovery".
"Recovery" gives me a menu (after reboot) where I could theoretically roll back to a previous backup for example.
"Bootloader" earlier gave me a text-based menu, where I could back my system up, now I can't reach this any more. The phone simply boots Cyanogenmod again.
Anyway, thanks and I'll try out TWRP!
Click to expand...
Click to collapse
well... the TWRP recovery is all you need if you wanna backup your system and restore later.
You won't need to use the 'Reboot to bootloader' option.
and Welcome
Hit the "Thanks" button if I helped.
Hi Zenith again,
I downloaded the zip-file and booted my cell phone into recovery mode.
Then I chose "Apply update" and the zip-file I had just downloaded.
It showed me a success, rebooting into recovery mode gave me the exact same menu ("Cyanogen recovery").
I probably did something wrong, but what?
Can you point me in the right direction, please?
Thx!
Edit: choosing "reboot to bootloader" in the recovery menu reboots the phone as before (not into bootloader)
Make sure you didn't select 'update cyanogenmod recovery' in the developer option, then go to http://forum.xda-developers.com/xpe...-twrp-f2fs-support-xperia-sp-huashan-t3150230 ,download the zip and flash it with cyanogenmod recovery. You can now live happily ever after with cyanogenmod and twrp recovey.
flash it back to stock rom and then root it via towelroot and installa superSU also check with any app if your phone is rooted or not then check if bootloader is unlocked and after that flash doomkernel (latest verson) after that flash any rom you want to test
steveglowplunk said:
Make sure you didn't select 'update cyanogenmod recovery' in the developer option, then go to http://forum.xda-developers.com/xpe...-twrp-f2fs-support-xperia-sp-huashan-t3150230 ,download the zip and flash it with cyanogenmod recovery. You can now live happily ever after with cyanogenmod and twrp recovey.
Click to expand...
Click to collapse
@steveglowplunk:
Thanks, that was what obviously kept replacing the recovery module.
I used the zip-file that Zenith linked to initially, though. It worked fine after that (hence the thank you to both of you).
@electro_nik:
I didn't want to go through the whole process again. I'm sure your way would give me back the original bootloader, but as long as I can create a backup, I think I'm fine. Thanks though!
Also never forget to CHECK ROOT ACCESS FOR ADB and USB DEBUGGING in the developer option. It can always save both your life and your phone's life when your phone is bricked
Hello everyone,
I have been using custom roms happily for a couple of devices for quite some time now. Now I have the ASUS rog2 and do have some trouble with it.
History:
I bought one a year ago and flashed it with various stuff and got happy with omnirom and it worked fine. I had trouble making TWRP permanent though. However, I did not care much about it, I keep data backups anyway.
At some day the phone software crashed and bricked itself. I could not boot the rom anymore and I formatted every partition and reflashed with TWRP. It failed. Every single time the best I could get was to get the device having a bootloop. I followed what I tend to read here, flash the rom twice on both partitions. I am not sure if that is actually needed If I switch the partition to the one I just flashed.
I then found out about the EDL and flashed the phone with the QPST/QFIL (I forgot which one) and the stock rom. This worked fine and the phone booted. Reflashing again with omnirom via TWRP got me back to bootloops again. So in the end I found myself happy with the stock rom, better than no phone. I used this for some time until I finally hard crashed my phone on the road. I now operate the phone on PC via SCRCPY and I got another ROG2.
Now here is my actual question, TLDR;
I want to flash it and basically went unlocking it, booting TWRP, formatting DATA, internal and caches - Flashed omnirom to both slots via ADB sideload. Now a similar thing happens. It does not even boot past the bootloader.
I flashed the latest stock rom from ASUS, released 27th of April, Android 11 and it boots up fine. I broke it again since I want to try nanodroid and probably did something wrong. No question about it.
What am I doing wrong in flashing a random not-stock-rom?
My experience is that usually it is the users fault, so I expect here I am doing something wrong, missing a stupid step.
I...
- boot TWRP with fastboot.
- flash a rom with ADB sideload, too lazy to copy the ROM to the internal storage. I think these are same anyway.
- reboot the phone, fastboot TWRP.
- flash a rom with ADB sideload to the other slot.
- Boot and fail
Appreciate help and insight on it. I like flashing and trying but I seem to have lost the idea of what I am doing with the A/B partitioning maybe or something with this phone series.
What I found out so far is weird.
Omnirom11 and 12 (just freshly released) can be flashed without error, but when I then look at the directory structure caused by this flash... there is none. As if nothing was written. Stock ROM leaves a directory tree as expected.
So /sdcard/Download, data ... etc. are not present.
Then depends on the TWRP versions: the twrp-3.4.0-0-I001D-Q-mauronofrio.img can be booted normally, it saves its settings on the disk normally. So make changes, reboot, the changes are present.
So far TWRP 3.6 made these changes but did not manage to store them.
When I ADB push a ROM to the phone onto sdcard root, the same funny thing happens. After reboot, the file is gone.
And weirder.... when I copy stuff via adb push to /sdcard/ it is visible over reboots only in the mentioned 3.4 TWRP. If I boot 3.6 then the /sdcard/ is empty. If I reboot back to 3.4, the files are visible.
Is there some problem with some sort of overlay space?
I think I found out why, although this is lazy guesswork.
Found a video by terminal_heat_sink and followed it original; you basically have to install the stock ROM on both slots. Then install omnirom OVER the stock rom. That is maybe how they get the camera, air trigger apps running inside omni (assumption only).
No replies, you are talking to your self.
Thanks for findings
Well, if I spent my time on it understanding it (I do hope so), then maybe it helps someone else and this doesn't end up as a soulless thread that has some xkcd 979 reminisence.