Having read the various forum postings here and on modaco site, I have a problem that I'm not managing to resolve regarding flashing my Gen 1 OSF with stock Orange 2.1 to a different rom.
Hoping one of the gurus/techs/wizards here could help? Please?
Here's what I did:
1. Rooted using Universal Androot including SuperUser
2. Used Rom Manager to flash ClockworkMod Recovery
3. Clicked on the backup current ROM button
Here's what happened:
1. Device rebooted once, came to green android screen and booted up very quickly, no backup on SD card
2. Using Rom Manager, tried to reboot into recovery, get 'An error occured attempting to run privileged commands!' message
3. Using Rom Manager, tried to flash new rom from SD card, get 'An error occured attempting to run privileged commands!' message
4. Tried to do a factory reset, device reboots, gets to green android screen (probably fails to get into recovery mode), reboots again and loads up as normal. Unable to factory reset
5. Tried to reboot with volume- into recovery mode. As long as volume- pressed, endless cycle of rebooting to green android screen - presumably can't get into recovery mode.
6. Tried to reboot with volume+, device boots up normally, Can't get into fastboot
7. Tried Recovery Manager, but App won't load with 'The application Recovery Manager (process com.podtwo.RecoveryManager) has stopped unexpectedly. Please try again. Force Close'. Keeps crashing and won't load.
Now stuck with device I can't update the ROM on and can't restore to factory settings.
Any suggestions as to how I could do either flash a new ROM or restore the stock ROM to factory settings, would be gratefully appreciated.
Is there any software I could use to restore to factory settings? Is there any other way of flashing the Swedish Spring RLS5 ROM?
Look forward to hearing your advice/comments/suggestions. Many thanks in advance (otherwise I'm forced to go back to my WinMo 6.1 device!)
UPDATE: problem solved by flashing clockworkmod image file using recovery manager.
Do you have more in depth instructions? I'm having the same problem on my San Francisco.
Sent from my GT-I9100 using XDA App
I just got the new CWM recovery update through Rom Manager today, and it said it was successfully flashed, but the phone only hangs on the HTC logo when goingto recovery. I can still do fastboot and boot to Android tho, so I'm now gonna try to figure out how to get my recovery back before something bad happes xD
anyone have advice or know where I can download a standalone copy of CWM 5.0.0.1 for G2?
Wish me luck I'll keep updating as things progress
okipokey, solved my own issue. Just had to reflash back to an older recovery and try again a couple times before it stuck.
Time to test out the new recovery!
I decided to flash the upgrade as well. The flash went perfectly. However, I couldn't boot into recovery while within Android. I had to power off and boot into the bootloader and then select recovery... Whenever I tried to reboot to recovery via the Android UI, it restarted and hung at the boot splash screen.. It didn't even work if you selected the option from the ROM Manager itself... I rolled back to previous version as well and its working again. It may be a bug... Early adopters nightmare....
Same here just reinstalled the new version and it worked second time round
must be a bug they havn't quite worked out. Next time I'll do a fastboot flash instead for a low build number.
First time I flashed I tried it from a battery pull through HBOOT and it still hung. Reflash to 3.5 and then back to 5.0 fixed it like you guys
epolaris said:
I decided to flash the upgrade as well. The flash went perfectly. However, I couldn't boot into recovery while within Android. I had to power off and boot into the bootloader and then select recovery... Whenever I tried to reboot to recovery via the Android UI, it restarted and hung at the boot splash screen.. It didn't even work if you selected the option from the ROM Manager itself... I rolled back to previous version as well and its working again. It may be a bug... Early adopters nightmare....
Click to expand...
Click to collapse
try just reflashing version 5 I had the same problem,but rebooted the phone reflashed version 5 from the rom manager and now is all good
I just sent the dev a comment about it on his Google+
maybe he'll have a fix out soon
Nice one, seems a "double flash" fixes it have just tested 3 or 4 times,seems to be working
yessir, seems to me that if it's a bug its really minor. I can see this being a problem if someone accidentally screws up something on their phone right after flashing the recovery, but not very likely and they'd still be able to reflash through fastboot
Seemed to flash the new version ok. But then, when trying to boot into recovery for the first time, the phone hung on the HTC logo boot splash. Pulled battery, and booted into recovery ok after that.
that's interesting that some of you didn't hang after the battery pull while mine did. Maybe it depends which version we're upgrading from?
stuck at htc
hey i also had this problem and i can't get my g2 to boot up at all. It hangs at the htc screen. I don't know how to fix this issue as i was trying to restore a backup from recovery right after the update. i can't get into recovery or anything else...all i get is the htc screen. Any ideas how I can fix this?
Luis
Any sign of a changelog?
I have no idea how to get to a changelog...can you tell me how?
biglou421 said:
I have no idea how to get to a changelog...can you tell me how?
Click to expand...
Click to collapse
found this
-From Mr.Dutta via G+
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
So far no issues here while playing around.
my issue is i can't get back to android at all now. i went into rom manager to restore a backup and was told there was an update, then it reflashed the recovery. When i tried to restore my backup it froze and i have not been able to get past the htc screen at all.
biglou421 said:
my issue is i can't get back to android at all now. i went into rom manager to restore a backup and was told there was an update, then it reflashed the recovery. When i tried to restore my backup it froze and i have not been able to get past the htc screen at all.
Click to expand...
Click to collapse
can you get into the HBOOT?
pull the battery, put it back in, hold the volume down button and then hit the power button. you should come to a white screen with some options
In the case you want to update your recovery using fastboot method, heres what you'll need:
CWM 5.0.0.1 for G2 (Vision)
HTC Sync drivers
ADB fastboot from Android SDK
Make sure your phone is all the way off by pulling the battery. Get into the HBOOT by holding down the volume down button and then hitting the power. use the volume keys to navigate and the power button to select. Choose "FASTBOOT"
Rename the recovery that you downloaded from CWM to "recovery.img" and put it in your ADB and Fastboot folder
plug your phone into your computer and pull up a command line for your adb/tools/ or adb/platform-tools/ folder where you should have ADB and Fastboot.
under the command line type in:
fastboot devices
<list of devices>
If you do not see your device make sure the cable is plugged in and your drivers are installed. if still nothing try a different cable til you get it to be recognized by the computer.
Once it's recognized do:
fastboot flash recovery recovery.img
when its done:
reboot
I flashed through ROM manager. On suggestion, I checked the box for "erase recovery - recovery will be erased prior to flashing". On first reboot to recovery it sticks at HTC screen. Pulling battery and vol. up+power then entering recovery the 2nd time works just fine.
Hope this helps.
greetings people,
a few days ago my friend brought me a phone for me to flash a custom rom onto it. I can't REGRET anything more then accepting this phone.
I rooted the phone on stock android 4.4.4 with Kingroot and after that, **** went down real bad.
I realised I couldn't acces recovery NOR download modus anymore, i try'd to boot into download/recovery with the hardware button way, but I also try'd to boot with adb reboot download / recovery
neither of those options worked, the phone either normally booted up or it kept trying to reboot with a black screen.
after I rooted it the boot image u get like " Samsung XXX "" were also gone.
after ALOT of searching and stuff and attempting things ive found a really old thread that stated to use fastboot reboot bootloader. I were really amazed that that worked but instead of booting up to the regular download modus it booted into fastboot, I read somewhere someone had the similair issue like me and they told him his boot img were corrupted. so ive headed to sammobile and downloaded the stock firmware for the device, I extracted the packages since I couldn't use odin because I am/was not able to acces download modus, while in fastboot i flashed the single boot.img with the command "Fastboot flash boot boot.img" it succeeded but after it succeeded I tried to boot it up but it fails booting to OS,recovery and download. it keeps attemping to reboot, I am CLUELESS at this point. I am able to try some things when I can enter that fastboot mode I had before but I can't acces the phone with ADB since it just keeps rebooting and stays inresponsible
I am planning to buy a USB JIGG, i use to have one but I can't find it anywhere.
any idea's/information would be soo helpful..
thanx in advance
Grand Neo Plus Root
a
omametsnor said:
greetings people,
a few days ago my friend brought me a phone for me to flash a custom rom onto it. I can't REGRET anything more then accepting this phone.
I rooted the phone on stock android 4.4.4 with Kingroot and after that, **** went down real bad.
I realised I couldn't acces recovery NOR download modus anymore, i try'd to boot into download/recovery with the hardware button way, but I also try'd to boot with adb reboot download / recovery
neither of those options worked, the phone either normally booted up or it kept trying to reboot with a black screen.
after I rooted it the boot image u get like " Samsung XXX "" were also gone.
after ALOT of searching and stuff and attempting things ive found a really old thread that stated to use fastboot reboot bootloader. I were really amazed that that worked but instead of booting up to the regular download modus it booted into fastboot, I read somewhere someone had the similair issue like me and they told him his boot img were corrupted. so ive headed to sammobile and downloaded the stock firmware for the device, I extracted the packages since I couldn't use odin because I am/was not able to acces download modus, while in fastboot i flashed the single boot.img with the command "Fastboot flash boot boot.img" it succeeded but after it succeeded I tried to boot it up but it fails booting to OS,recovery and download. it keeps attemping to reboot, I am CLUELESS at this point. I am able to try some things when I can enter that fastboot mode I had before but I can't acces the phone with ADB since it just keeps rebooting and stays inresponsible
I am planning to buy a USB JIGG, i use to have one but I can't find it anywhere.
any idea's/information would be soo helpful..
thanx in advance
Click to expand...
Click to collapse
Hi There, I just came across your thread, because I'm in the same position you are, fortunately though, I've managed to root this phone without any problems, however it seem though that there is no custom ROM available for this device, at least nothing past KK, and that one I found didn't seem so stable, I tried to flash it and came back with an error!! So my friend won't be able to bring his phone out of the Dark Ages!! at least it's Rooted! and now he may be able to use some apps that do require root, It's the best I can do at this point. I used the link below to root sucessfully:
https://www.google.com/url?q=http://forum.xda-developers.com/android/general/root-galaxy-grand-neo-plus-gt-i9060i-ds-t3070302&sa=U&ved=0ahUKEwjds_Tn-sDOAhVG1B4KHe8xDC0QFggEMAA&client=internal-uds-cse&usg=AFQjCNFDnwTNwiFG6H8TI_hKXAeeWEOlRw
I realize it's kinda late but luck to you my friend:fingers-crossed:
By the way, This one is the Dual Sim Version, don't know if that will make a difference?!
Hey guys I was trying to flash MIUI 8 on my a6000 lenovo. Bear with me because I'm new to this so I might have screwed up.
Rooted and installed TWRP perfectly. Phone was running kitkat.
I then, through TWRP tried to flash MIUI 8 from http://forum.xda-developers.com/lenovo-a6000/development/rom-miui-7-lenovo-a6000-a6000-t3355692
After first swiping right to install the zip, i got an "error executing binary in zip" error. Wiped dalvik,etc. again and tried again and then I got a MD5 file not found "warning". It was not in red letters and after that message there was no progress bar or anything and the phone just stopped responding. I assumed it wasn't working and few minutes later took the battery out. After trying to boot again it would give me the "mi.com" boot screen (not the default lenovo I used to get) and won't boot into neither recovery nor normal mode. (for recovery boot I'm trying holding both volume buttons and the power button at the same time. perhaps that is different now?)
I'm guessing the flashing was going on and i interrupted it. How can I fix this?
Update: It boots into MIUI now however pretty much nothing works as expected. It wont even go into settings. Recovery still seems botched and i cant boot into it.
TLDR: Recovery broken cant boot into it. Can boot into MIUI with very limited capabilities. Cannot select USB debugging and "adb devices" won't find the phone. What can I do?
Alright nevermind guys I managed to fix it. for anyone wondering or having the same issue, i tried many things but what I think worked is this:
Turnt on my phone in fastboot mode (hold volume - and power button) , connected it to the computer and used command "fastboot flash recovery recovery.img" to flash the old TWRP i had on my computer. After that I managed to boot my phone in recovery mode and reflash the rom properly. The weird thing is, my phone could not be recognized by the computer and "adb devices" gave me nothing back so I thought using any fastboot command wouldn't work. Oddly, it did and it flashed TWRP back into my phone.
hello,
as the title says, my phone bricked while trying to go back to stock rom. this is what i did: i had a well working meticulus custom rom + the meticulus twrp recovery on my phone. thing is i need the google apps and they are not supported on meticulus roms. so i tried to go back to rom, downloaded a stock rom and tried to flash it with dragging it onto my sdcard and installing it from there. so this is when it bricked, the huawei logo appears at the start but it stays and nothing will install.
i tried to reinstall the adb drivers, no success. i can only use the bootloader but i can only flash a recovery, after trying to boot into the recovery via fastboot boot recovery.img it won´t do a thing. also the recovery is stock recovery all of a sudden (erecovery). and there i only have the option to "download latest version and recovery" but that gives an error aswell.
i´ve tried to reinstall drivers, no luck. when i do a fastboot devices it shows my device but when i do adb devices it doesn´t show up anything. so the usb driver is somewhat corrupted. my computer detects the phone when in fastboot only.
i´ve tried to reinstall the drivers a hundred times, i can´t get the phone to work anymore.
i would really appreciate it if someone helps me out.