Related
Hi everyone, I have a rooted nexus S with stock image of 2.3.1. I've installed Kernal Manager app from the market to install CM7. The phone restarted and got stuck with the "Google" logo and a lock icon below.
Below is what I get when reboot through volume up.
________________________________
FASTBOOT MODE:
PRODUCT NAME - HEARING
HW VERSION - REV 11
BOOTLOADER VERSION - 19020XXJK1
BOOTLOADER BUILD - Nov 4 2010
BASEBAND VERSION 19020XXJK8
SERIAL NUMBER - blablabla
LOCKSTATE - UNLOCKED
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB control init
USB control init
STANDARD_SET_CONFIGURATION
______________________________
The only option I could progress on those 4 options is by going through recover, but then it stops there with a triangle sign.
I clicked power or volume together again and got more options below:
_______________________________
Android system recovery <3e>
reboot system now
apply update from /sdcard
wipe data/factory reset
wipe cache partition
__________________________________
I can't update anything from my data and wiping the data had no effect either.
In another note, My PC is windows 7 64 bit and installed with SDK and drivers only until now. My android is recognized by my PC but when I type "fastboot devices" in CMD under the tools path nothing happens so if I type "fastboot oem lock" or "unlock" it will wait for device forever.
Please help me, this is the only phone I have.
does the phone connect at all when you are in recovery via command: "adb devices" ?
If you are in clockwork recovery then wipe these areas.
1. wipe factory data
2. wipe cache partition
3. in the advanced tab wipe dalvik cache
4. go to install from sdcard and find the cm file and flash the rom again.
side note. If installing cm7 then the gapps have to flashed also.
I have never used kernel manager so don't know how it went about flashing gapps.
.
This guide may be of some help. http://wiki.cyanogenmod.com/index.php?title=Nexus_S:_Full_Update_Guide
jerrycycle said:
If you are in clockwork recovery then wipe these areas.
1. wipe factory data
2. wipe cache partition
3. in the advanced tab wipe dalvik cache
4. go to install from sdcard and find the cm file and flash the rom again.
side note. If installing cm7 then the gapps have to flashed also.
I have never used kernel manager so don't know how it went about flashing gapps.
.
This guide may be of some help. http://wiki.cyanogenmod.com/index.php?title=Nexus_S:_Full_Update_Guide
Click to expand...
Click to collapse
Looks to me like OP doesn't have clockwork installed.
ganbachi said:
Hi everyone, I have a rooted nexus S with stock image of 2.3.1. I've installed Kernal Manager app from the market to install CM7. The phone restarted and got stuck with the "Google" logo and a lock icon below.
Below is what I get when reboot through volume up.
________________________________
FASTBOOT MODE:
PRODUCT NAME - HEARING
HW VERSION - REV 11
BOOTLOADER VERSION - 19020XXJK1
BOOTLOADER BUILD - Nov 4 2010
BASEBAND VERSION 19020XXJK8
SERIAL NUMBER - blablabla
LOCKSTATE - UNLOCKED
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB control init
USB control init
STANDARD_SET_CONFIGURATION
______________________________
The only option I could progress on those 4 options is by going through recover, but then it stops there with a triangle sign.
I clicked power or volume together again and got more options below:
_______________________________
Android system recovery <3e>
reboot system now
apply update from /sdcard
wipe data/factory reset
wipe cache partition
__________________________________
I can't update anything from my data and wiping the data had no effect either.
In another note, My PC is windows 7 64 bit and installed with SDK and drivers only until now. My android is recognized by my PC but when I type "fastboot devices" in CMD under the tools path nothing happens so if I type "fastboot oem lock" or "unlock" it will wait for device forever.
Please help me, this is the only phone I have.
Click to expand...
Click to collapse
Follow this guide to the letter - forum.xda-developers.com/showthread.php?t=895545
Try reinstalling the drivers with PDAnet. You need to get fastboot working. Its easy from there.
Sent from my Nexus S using XDA App
Hey Everyone,
Im sorry in advance if I'm about to ask the dumbest questions of the day/week, but I'm brand new to this, and I haven't found any answers in any of these threads, so go easy...
Up until now I customized the heck out of my mt4g. Tonight however, I followed HTC's instructions and unlock the boot loader -- as I thought based on what their site said, that I'd be able to flash custom roms to the phone once unlocked.
I was successful in unlocking the Bootloader, but (S=on) still exists. I'm kinda stuck now because I don't know what to do next? Is it possible to go from here to Root, if so, how? I've tried the HTC Super Tool for over an hour and it's not working... not giving me perm S=off. Maybe I'm doing something wrong?
If the phone isn't rooted, then how am I supposed to be able to flash a rom??... Do I do it from the HBOOT menu? Because I can't seem to do that either. If I opt for "recovery" while in HBOOT, I come to a red triangle, and have to do a battery pull.
The stock rom that's loaded now has GB 2.3.4 running.
My goal is simply to get CyanogenMod running on this phone. I just don't know what the next step is. I've already factory reset the phone so all my customizations and apps are gone therefore I don't really care what I have to do to get where I want to go. If it's possible to root from here, what's the next step? If root isn't possible, then how do I flash a new rom, like HTC claims I can do now that the BL is unlocked??
If someone could offer some help, I would be super appreciative!!
T40
Follow this link . Very well written guideit worked for me http://forum.xda-developers.com/showthread.php?t=1178912
headcreepz said:
Follow this link . Very well written guideit worked for me http://forum.xda-developers.com/showthread.php?t=1178912
Click to expand...
Click to collapse
Follow that guide and get off the official HTC unlock. You should have read the thread on this forum about it.
Sent from my mytouch 4g using xda premium
okay... I followed the guide and I achieved "perm-root", I believe.
If I go into terminal emulator, and type SU, I get a # returned. I do notice however that when I boot into HBOOT, it still says s=on. Not sure what the difference is between 'perm root' and 's=on' but...
I have rom manager downloaded. I also have titanium backup downloaded and did a full backup.
PROBLEM:
In rom manager, I Flashed ClockworkMod Recovery, and then downloaded the nightly CyanogenMod, no problem, but every time the phone reboots (into recovery mode), I stop at the red triangle?!?!?!
What's going wrong?
Open rom manager and art the top is an option to install recovery-install it, then you should be good to go
I did install recovery. Everytime it reboots into recovery i get the red triangle.
After I get the red triangle, and I hold the Vol Up button and hit power, I come to a BLUE recovery menu (3e) with 4 options:
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
in the middle of the screen, in yellow text it says "E:Can't open /cache/recovery/command"
track40 said:
I did install recovery. Everytime it reboots into recovery i get the red triangle.
After I get the red triangle, and I hold the Vol Up button and hit power, I come to a BLUE recovery menu (3e) with 4 options:
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
in the middle of the screen, in yellow text it says "E:Can't open /cache/recovery/command"
Click to expand...
Click to collapse
That's the stock android recovery.
Sent from my Infernalized Glacier!
-Team Inferno
If you had your device s-off and rooted, why HTC unlock? You just went backwards.
i started with HTC Unlock, then achieved perm-root, but (s=on)
Recovery
Hello,
I had the same issue, I had to flash the recovery with adb
1) If you dont already have it download flash_image and place it in your adb tools folder
2) Download the recovery you need and unzip, then rename to recovery.img and place in the root of your sdcard
3) open terminal and use the following commands
adb push flash_image /system/bin
adb shell
su
cd /system/bin
chmod 777 flash_image*
flash_image recovery /sdcard/recovery.img
4)wait for it to finish
5) type exit
adb reboot recovery
this should solve the issue
You can find the recovery here...including the new touchscreen version
http://clockworkmod.com/rommanager
You can download flash_image here
http://forum.xda-developers.com/showthread.php?t=902493
Thanks to Raichison for all the above
okay #furydude39, im all ready to run through your steps... when i issued the first command "adb push flash_image /system/bin", the handset responded with
"failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system"
Any idea where to go now? This is obviously why every time i boot into recovery that the processes initiated by RomManager isn't sticking.
an hour later...
I was able to execute the commands correctly that 'furydude39' recommended, and still nothing.
Here's a video I shot of the phone [still] giving me a headache
http://youtu.be/2Hr-7CosDQc
Someone's gotta have an idea on how to get past this?
Have you turned off fastboot?
Sent from my HTC Glacier using xda premium
yes, just checked... fastboot is off
We need to find out why it is not flashing the cw recovery. Are you able to to mount /system partition and copy files to it? I'm thinking a downgrade might be necessary so you can do gfree and eng bootloader.
Sent from my HTC Glacier using xda premium
okay guys...
I got past the last problem, of getting clockwork mod recovery to work. So, that's all set.
NOW, I use rom manager and i downloaded cyanogenmod 7.1 (stable) + google apps. Once the downloads were complete, I checked all three boxes... backup, clear caches, clear dalvik cache. The phone reboots, goes right into clockwork mod recovery.
the backup goes fine... the cyanogen flash goes without error, and then the google apps flashes without error.
NOW, the phone reboots, and the thing just hangs on the White t-mobile boot screen. Is this supposed to take a while before it goes into Cyanogen's screen? It's been sitting on this white screen for at least 5 minutes.
track40 said:
okay guys...
I got past the last problem, of getting clockwork mod recovery to work. So, that's all set.
NOW, I use rom manager and i downloaded cyanogenmod 7.1 (stable) + google apps. Once the downloads were complete, I checked all three boxes... backup, clear caches, clear dalvik cache. The phone reboots, goes right into clockwork mod recovery.
the backup goes fine... the cyanogen flash goes without error, and then the google apps flashes without error.
NOW, the phone reboots, and the thing just hangs on the White t-mobile boot screen. Is this supposed to take a while before it goes into Cyanogen's screen? It's been sitting on this white screen for at least 5 minutes.
Click to expand...
Click to collapse
You should manually wipe and flash. Doing it from the app seems to screw up some of the time. Make sure you wipe system data cache and dalvik before flash. It even helps to reboot recovery after doing wipe before you flash a rom.
Sent from my HTC Glacier using xda premium
i hate to ask another [stupid] question... but how do i manually do that?
track40 said:
i hate to ask another [stupid] question... but how do i manually do that?
Click to expand...
Click to collapse
In recovery, using the volume rockers, look for factory data reset/wipe. I'm not to positive on the exact names, since I have touch recovery. When you find it select wipe data an wipe cache. after those are wiped, go back then find advance, wipe dalvik cache. When that finished, go back. Select install from sdcard, find your files an install them. Everything should work then.
If I helped, give thanks, if you please.
........Death before dishonor........
Team inferno
Leader
Thanks all for your suggestions. I finally was able to get Cyanogen to stick. Had to wind up flashing the boot.img manually using fastboot via Windows while in HBOOT screen.
Hello XDA community !
LAst week I bought my Acer A700, but after a few days a dead pixel appeared...
So I was on my way to send back my toy, when I saw that CMWR was available.
"Nice ! I can do a factory reset so my toy will be clean to be sent back !"
But the factory reset didn't work... It was stuck at "Formatting /data" for a while...
So I rebooted the A700, and now it's stuck at the ACER logo... I only have access to recovery...
Any ideas ?
Thanks a lot :good:
Since you have recovery try and do data wipe, then wipe cache then davlik cache, then reboot.
If you have recovery you can install a ROM by renaming it update.zip and using CWM.
Itchiee said:
Since you have recovery try and do data wipe, then wipe cache then davlik cache, then reboot.
If you have recovery you can install a ROM by renaming it update.zip and using CWM.
Click to expand...
Click to collapse
I already tried this, when I want to install a update.zip, it stucks at "installing update".
When I want to wipe a partition, it stucks at "formating /xxx" and nothing happens...
I wanted to flash stock bootloader with Nvflash, but I can't find APX drivers for ACER A700
Can you install the update.zip without the use of CWM (By pressing the powerbutton with the vol down)?
Also, where is your update.zip located?
Edit:
I guess it could do no harm if you'd hook up your device to the PC and enter the following commands:
adb reboot bootloader
fastboot erase cache
Click to expand...
Click to collapse
TomONeill said:
Can you install the update.zip without the use of CWM (By pressing the powerbutton with the vol down)?
Also, where is your update.zip located?
Edit:
I guess it could do no harm if you'd hook up your device to the PC and enter the following commands:
Click to expand...
Click to collapse
_ update.zip putted on a extrenal SD card doesn't work, it's skipped and CWM is launched.
_ the "adb reboot bootloader" puts the A700 in "APX" mode... and the "fastboot erase cache" is stuck at "waiting for device"...
Thanks for trying to help !!!
May this be a relevant solution??
http://androidforums.com/esteem-all...w-get-out-clockworkmod-recovery-bootloop.html
Edit:
I don't think the device checks for update.zip on the sdcard. Maybe there is a way to move the file to the internal. (adb mount sdcard adb push /sdcard/update.zip update.zip ?
Yeah,
The current CWM seems to corrupt the Data partition (amongst other things). Seems to be a going thing lately. Remember, these are new tabs, and new root & recovery methods, so there are going to be some bricked tabs before things get sorted out. This happens in "ALL" development, and everybody knows the risks involved.
I had the same issue. Couldn't reboot into fastboot, as it seems the OS has to be running?
This is why Skirlax_CZ built the bootloader for the 500/501, so you could boot it into fastboot mode, bypassing the OS. Unfortunately, the stock 70x OEM bootloader doesn't seem to allow this.
Best bet if you can't find the "exact" version rom the tab was shipped with, is to try renaming some full roms to update.zip, copy to sd, reboot (vol + and PWR, and see if it will install and boot. At the worst, it will install a stock bootloader and recovery.
Also, holding PWR, Vol - (I believe) and toggling the rotation lock should wipe User Data.
At the very worse, turn it into Acer Service, suck it up and pay the repair bill.
They will just install the correct service rom and give it back to you.
MD
Touns said:
Hello XDA community !
LAst week I bought my Acer A700, but after a few days a dead pixel appeared...
So I was on my way to send back my toy, when I saw that CMWR was available.
"Nice ! I can do a factory reset so my toy will be clean to be sent back !"
But the factory reset didn't work... It was stuck at "Formatting /data" for a while...
So I rebooted the A700, and now it's stuck at the ACER logo... I only have access to recovery...
Any ideas ?
Thanks a lot :good:
Click to expand...
Click to collapse
your situation is just same as mine,seeming bricked after using fatory rest or wiping from cwm,I think it's the problem of the damn cwm.as i know from now there are several devices got bricked,all because of the goddamn cwm.as we know factory rest is the same as recovery wiping,i use the under the official recovery,everything wen fine,but after wiping via cwm from the forum,it appeared the problem.
i tried a lot of method,just as u mentioned,to flash *.img
but i found a curious thing,after dumping series of *.img from a well-mailfuntioning device i can use fastboot to flash "userdata" which the loaction is mmcblk010 or /dev/block/platform/sdhci-tegra.3/by-name/UDA,but after flashing,i can't erase userdata block in fastboot.then i reflashing the data.img to userdata block,then in cwm,i can mount /data,but it's still not able to wipe or format it.then i've found a data.img and flashing the userdata and reboot.then i enter the system,and it forced me to do a factory reset,of course as before,it's not mailfunctioning because of the cwm or the block itself damaged..
but i can enter adb,and i found that i can see the /data and the filesystem in it.then i use mount to modify it,for i can delete or modify the files in /data,and it appears normally.i delete everything in /data.then i want to try to reboot to see if it's working,but after rebooting,the device stuck at acer logo,then i reboot into the cwm,it can't be mounted again.it seems that i can flash the userdata but i can't format or wipe or modify...
and i tried to reflash the bootloader from a well-mailfunctioning deivece,not working,either.
then i go for searching the situation in google,i found there are a lot of similar problems of the tegra device,and the solution is nvflash...
i don't know if there are a block saving the information of partitions just like the PIT file of my galaxy s2,seems we should wait for nvflash?or the method to flashing PIT partitions file?
i installed the nvflash driver by modifying the usb id,but i can't do anything from nvflash,it's not matching.
I had the same problem after I upgraded to JB with CWM recovery 6.0.14 and I tried to root it. But it stuck in acer logo. Then I went to recovery mode, but it couldn't mount sdcard or external card, too.
In my case, I solved it by these steps:
1. Try to go to fastboot mode by press vol (-) + power. After it vibrate, release power, and then play lock button. Then tablet will go to fastboot mode. http://forum.xda-developers.com/showthread.php?t=1861092
2. Download these boot and recovery images: https://www.box.com/s/3321wf8gg4at639nfn06
3. Try to flash these boot and recovery images to table:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
And then, reboot tablet:
fastboot reboot
WOW, my tablet works again.
:victory:
kwaiding said:
I had the same problem after I upgraded to JB with CWM recovery 6.0.14 and I tried to root it. But it stuck in acer logo. Then I went to recovery mode, but it couldn't mount sdcard or external card, too.
In my case, I solved it by these steps:
1. Try to go to fastboot mode by press vol (-) + power. After it vibrate, release power, and then play lock button. Then tablet will go to fastboot mode. http://forum.xda-developers.com/showthread.php?t=1861092
2. Download these boot and recovery images: https://www.box.com/s/3321wf8gg4at639nfn06
3. Try to flash these boot and recovery images to table:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
And then, reboot tablet:
fastboot reboot
WOW, my tablet works again.
:victory:
Click to expand...
Click to collapse
Unfortunately, although somewhat similar, this is not the same situation as the OP had.
The first CWM originally posted a few months ago, was posted by a user who used the totally wrong partition tables, and also, didn't own the tab so it was never tested (after the fact). Basically, it damaged the chipset which required a motherboard replacement. Not to mention a specifically nasty Data_Cap bug in the CWM kernel. No image flashing via fastboot (and probably NVFlash) would repair the damage. The result was several bricked tabs till the CWM was removed. (mine included)
Also note, that the current root procedure is by the same person. Although there is an alternative.
What you had, was simple data corruption on one of the Dev Blocks. This is why you were able to fastboot an image.
Corrupting a partition can happen at any time. Whether rooted, stock, or custom rom. So it's always nice to have ADB to pull your partition images. Just in case.
MD
Hey guys, I'm fairly new to this but I have my One S, H-Boot 1.18, Radio 1.08, unlocked, rooted, TWRP2.4.4.0 and S-Off...
I have successfully installed CM10, and have since restored it to the Stock RUU.
I have tried loading the Viper 2.1.0 5 times now and keep getting stuck on the "white "T-Mobile screen" with the red text on it. I have a few questions about the instructions that are posted.
1. Download the Boot.img Flash Script from http://androidfilehost.com/?fid=9390275921635705217
2. Download the Rom
3. Extract the Boot.img Flash Script on your PC
4. Connect your One S to the PC (USB Disk Mode), copy ViperOneS_xx.zip (the ROM) to your HTC One S
5. Connect your One S via USB and ensure you have HTC Sync installed, you need the drivers to be able to use fastboot
6. Uncheck fastboot in Settings->Power, then shut down your HTC One S completely (don't reboot, shut it down).
7. Press and hold volume down, then press power (keep holding volume down!) until your screen shows the hboot menu, navigate to recovery (use volume keys)and press the power button once to jump into recovery mode.
8. In Recovery choose install zip from sd -> choose zip file and navigate with your volume buttons to the downloaded Rom and hit power and confirm with yes.
I am using TWRP 2.4.4.0 which is supposed to be problem free (something about they fixed the .lib issue from the previous version that the new JB created), I have been wiping System and recovery.
9. Now the Aroma installer should show, if you have the touch recovery installed you can use your screen to navigate through it, otherwise use the volume buttons and confirm with the power button.
I'm confused on the Kernel prompt during the installation, doesn't the boot.img file that we install in the next step have a new Kernel in it? So do I sellect a custom Kernel or not?
IMPORTANT: if you come from another Rom, pls choose FULLWIPE
10. After you configured it, reboot to your bootloader in fastboot mode
11. Now go to your extracted Boot.img Flash Script folder:
Depending on your OS of your PC you need to run the file like normal:
Windows: flash-boot-windows.bat
MAC: flash-boot-mac.sh
Linux: flash-boot-linux.sh
12. When the commands were successful, press power again to go back to the hboot
13. Navigate with your volume button to "Recovery" and reboot or reboot via cmd with "fastboot reboot"
14. Finally we highly recommend specifically for One S to boot again in recovery and wipe cache. Please do that also, whenever you flash any addons or mods – always boot your device first, then boot again in recovery and wipe cache.
15. Recommendation - with "Flash Image GUI" from joeykrim you can alternatively flash boot.img on your device, no need to fastboot anymore - http://forum.xda-developers.com/show...1954121&page=2
This recommendation Should be in the beginning right? Doesn't this flash the Kernel and then tell you to install the ROM directly afterwards? So shouldn't this be step one?
Any advice, appreciated, I'm not stopping until this thing is a brick or I figure it out...
thanks ahead of time, and I have tried to read through there are almost 600 posts so if I missed something I apologize ahead of time.
I know exactly how you feel..I went through the same issues as you did. Below are my feedback on what I did, however as I found through other posts, instructions may work for some, but not all phones. So please be careful if you were to follow what I did. I put my feedback in blue and my own direction list on what I did that finally made viper one s work for me.
1. Download the Boot.img Flash Script from http://androidfilehost.com/?fid=9390275921635705217
2. Download the Rom
3. Extract the Boot.img Flash Script on your PC
4. Connect your One S to the PC (USB Disk Mode), copy ViperOneS_xx.zip (the ROM) to your HTC One S
5. Connect your One S via USB and ensure you have HTC Sync installed, you need the drivers to be able to use fastboot
6. Uncheck fastboot in Settings->Power, then shut down your HTC One S completely (don't reboot, shut it down).
7. Press and hold volume down, then press power (keep holding volume down!) until your screen shows the hboot menu, navigate to recovery (use volume keys)and press the power button once to jump into recovery mode.
8. In Recovery choose install zip from sd -> choose zip file and navigate with your volume buttons to the downloaded Rom and hit power and confirm with yes.
I am using TWRP 2.4.4.0 which is supposed to be problem free (something about they fixed the .lib issue from the previous version that the new JB created), I have been wiping System and recovery.
Alright, seems like it's good then, I used CWM to make mine work but I'm pretty sure that you'll be fine with that one.
9. Now the Aroma installer should show, if you have the touch recovery installed you can use your screen to navigate through it, otherwise use the volume buttons and confirm with the power button.
I'm confused on the Kernel prompt during the installation, doesn't the boot.img file that we install in the next step have a new Kernel in it? So do I sellect a custom Kernel or not?
This is what I figured out, as I had the same question when I was going through the installer.
-Yes: Means that you come from a kernel that is not the normal kernel, such as ElementalX.
-No: Means you are using the stock kernel.
Selecting yes will skip the new flashing of the boot.img kernel, while selecting no will flash the boot.img
IMPORTANT: if you come from another Rom, pls choose FULLWIPE
Actually this part was the game changer for me, instead of following this, I wiped the system using my recovery, then selected install without wiping. (As I already wiped it via recovery)
10. After you configured it, reboot to your bootloader in fastboot mode
Even though I have seen numerous posts saying that once the One S is S-off you don't need to boot-flash-script..I clicked restart on the aroma installer and pressed the volume down button and the power, went into boot loader, went into fast boot USB and installed the boot-flash-script anyways..doesn't hurt
11. Now go to your extracted Boot.img Flash Script folder:
Depending on your OS of your PC you need to run the file like normal:
Windows: flash-boot-windows.bat
MAC: flash-boot-mac.sh
Linux: flash-boot-linux.sh
12. When the commands were successful, press power again to go back to the hboot
13. Navigate with your volume button to "Recovery" and reboot or reboot via cmd with "fastboot reboot"
14. Finally we highly recommend specifically for One S to boot again in recovery and wipe cache. Please do that also, whenever you flash any addons or mods – always boot your device first, then boot again in recovery and wipe cache.
15. Recommendation - with "Flash Image GUI" from joeykrim you can alternatively flash boot.img on your device, no need to fastboot anymore - http://forum.xda-developers.com/show...1954121&page=2
This recommendation Should be in the beginning right? Doesn't this flash the Kernel and then tell you to install the ROM directly afterwards? So shouldn't this be step one?
For me, I ignored that, because of that I have no knowledge for this question. :/
I am going off knowledge of what I did, as I had the same trouble you did. I tried to flash the rom countless times, almost bricked my phone, but after a stressful trial and error, I found the bugs that gave me my problems.
My Directions
1. Make nandroid (Just in case rom doesn't work)
2. Backup all apps as wiping phone will wipe all data and apps
2. Put viper 2.1.0 on device folder (I made a folder called roms)
3. Go to recovery
4. Wipe cache, system, and dalvik
5. Start the installer
4. Run through the desired checklists
-Select continue without wipe
-If on normal kernel select no when prompted on the kernel checklist
5. Once complete, click restart
6. Press and hold volume down and power to go to boot loader
7. Install boot-flash-script
9. Start Phone
10. It will be wiped, so go through the HTC start-up instructions
11. Once all that is done and the phone is fullyloaded, boot phone to recovery
12. Wipe Cache (to lessen lag)
13. Reboot again and done!
Don't use twrp 2.4.4.0, there are known problems flashing with it. Go for 2.3.3.0
First Thanks to both of you for the help.
So I down graded to TWRP 2.3.3.0...
Backed up my phone
Restarted phone, mounted and deleted the old back up
Began following the modified instructions
It appeared to work a little better this time ie... The installation screen colors seemed to be right and not all in a blue hue, and when it loaded it went all the way to 100% instead of hanging at 7% and then saying done.
I want to make sure this is correct also when I run the fastboot script, that this is what it should look like...
C:\htc_one\One_S_All-In-One_Kit_v3.4\Data>fastboot flash boot boot.img
< waiting for device >
sending 'boot' (6124 KB)...
OKAY [ 0.850s]
writing 'boot'...
OKAY [ 1.475s]
finished. total time: 2.328s
Alas this is still a "no joy" situation.
only good news is that I'm not stuck at the T-Mobile screen any more, the screen goes away after 5 seconds and now I'm sitting on a black screen.
What this has led me to think is that either the rom did not install correctly (duh) or you just downloaded the update for viper one s instead of the whole rom.
So just for clarification, now instead of on the t mobile screen it now goes to a black screen?
-Have you gone back into recovery and wiped cache again?
-Do you have a custom kernel or the stock kernel?
On another note.. Yes, the fastboot script was correct.
Sent from my HTC One S using xda app-developers app
So, I got it working, it seems that because I have my phone in S-Off, I didn't need to run the script. I just let it reboot after reinstalling it and it came up just fine.
I really appreciated the help guys, great support here... Maybe this post itself will help someone. :good:
Hello,
Yesterday there was an update for the Moto G, I confirmed to do the update. Since then the phone is in a reboot loop. I mean it doesn't matter what ever I do,the phone restart itself in every 2-3 minutes. The phone is rooted.
I've tried to do a factory reset from the setting,however nothing happens when I want to erase the settings. In the bootloader if I chose Recovery or Factory reset,the phone reboots.
I've got a tip that I should remove the update file from the /chace directory,however I don't know how to do so,as the phone keeps reboot itself.
The only place,where the phone is not restarts is in the bootloader.
Is there any way to somehow solve this problem without flash a stock rom ?
Thanks for your help!
Regards,
Péter
The same here. Help!
Tussky said:
Hello,
I've tried to do a factory reset from the setting,however nothing happens when I want to erase the settings. In the bootloader if I chose Recovery or Factory reset,the phone reboots.
Click to expand...
Click to collapse
You have to press volume up instead of power to choose something in fastboot menu.
Unroot and if used custom recovery go back to stock recovery.
mokkami said:
Unroot and stock recovery.
Click to expand...
Click to collapse
How should I do the unroot ? I find this solution,but I can't post the link,as I didn't have 10+ posts... its in the site unlockr and there's an article about moto g unroot.
However I can't enable the usb debug,as the phone restart faster,than I'am able to do this.
Yes I know I have to press volume up,however if I chose recovery it's reboot itself,so I'am not able to select Recovery from the bootloader.
Tussky said:
How should I do the unroot ? I find this solution,but I can't post the link,as I didn't have 10+ posts... its in the site unlockr and there's an article about moto g unroot.
However I can't enable the usb debug,as the phone restart faster,than I'am able to do this.
Click to expand...
Click to collapse
My is rooted and cwm 6.0.4.6
May be we must do something with fastboot command
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
If you havent installed, CWM or TWRP, then I recommend to do so by fastboot command and the recovery.img.
Here is the forum link to install CWM Recovery for your Moto G:
http://forum.xda-developers.com/showthread.php?t=2563599
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Fastboot menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
I think I will install CM11 for her and not have to deal with the stock ROM that gets official updates pushed onto it causing issues like this.
eyeoncomputers said:
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Recovery menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
Click to expand...
Click to collapse
I see,however It's not possible on the phone. If I select the Recovery and I press volume up -> phone reboots
You mean this.
Download Stock image, extract.
Go to fastboot mode and flash following.
If you used Superboot method then use:
fastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
if you used the modified recovery method:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Tussky said:
I see,however It's not possible on the phone. If I select the Recovery and I press volume up -> phone reboots
Click to expand...
Click to collapse
Thats strange.
eyeoncomputers said:
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
If you havent installed, CWM or TWRP, then I recommend to do so by fastboot command and the recovery.img.
The general command to install a custom recovery in Fastboot is:
fastboot flash recovery your_recovery_image.img
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Fastboot menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
I think I will install CM11 for her and not have to deal with the stock ROM that gets official updates pushed onto it causing issues like this.
Click to expand...
Click to collapse
Thanks MAN! It works perfect!
mokkami said:
You mean this[/URL].
Download Stock image, extract.
Go to fastboot mode and flash following.
If you used Superboot method then use:
if you used the modified recovery method:
Thats strange.
Click to expand...
Click to collapse
Yes, I mean that,so if I follow this guide,then it will help ? I used the followin from modaco site -> Root your Moto G - option 1: Superboot
@kokonai OH? I thought unroot is essential?
I guess u used the modified recovery to root?
Tussky said:
Yes, I mean that,so if I follow this guide,then it will help ? I used the followin from modaco site -> Root your Moto G - option 1: Superboot
Click to expand...
Click to collapse
At the moment i am confused. But yeah i'm assuming it will work.
Cause if i understand it right, the superboot method is a modified kernel.
So you should flash motoboot.img.
There are several ways now. Either you flash cwm and wipe /cache as described above.
Or you flash motoboot and then , in my opinion, it should work.
mokkami said:
@kokonai OH? I thought unroot is essential?
I guess u used the modified recovery to root?
At the moment i am confused. But yeah i'm assuming it will work.
Cause if i understand it right, the superboot method is a modified kernel.
So you should flash motoboot.img.
There are several ways now. Either you flash cwm and wipe /cache as described above.
Or you flash motoboot and then , in my opinion, it should work.
Click to expand...
Click to collapse
I used the method to root the phone what is on that site,I followed that description and it worked. I'am not an expert in it,so I just followed PaulOBrien guide,so I can't answer for it for sure.
At this point I'am really desperate as the phone is completely useless, so I don't care even if I had data loss,as I can't access it anymore,nor save it to my PC.
In my knowledge, which seems not to be true anymore, the phone needs to be stock to install any update.
I am not talking about installed apps. It is more about system partition, recovery, kernel and so on.
I would try now to flash the motoboot.img and see what happens.
If this does not work i would flash cmw and try what was mentioned above.
Sure you can go completly stock. But in my view you are not that lost.
I'll stay with you
......but max 5 hours =)
mokkami said:
In my knowledge, which seems not to be true anymore, the phone needs to be stock to install any update.
I am not talking about installed apps. It is more about system partition, recovery, kernel and so on.
I would try now to flash the motoboot.img and see what happens.
If this does not work i would flash cmw and try what was mentioned above.
Sure you can go completly stock. But in my view you are not that lost.
I'll stay with you
......but max 5 hours =)
Click to expand...
Click to collapse
Thanks! However I can try it out only after 20 UTC.
However I have an idea,but maybe I'am wrong.
What happens if I try the chace wipe via in command line, I mean:
mfastboot erase cache
This should delete the cache right ? Shouldn't this command remove the problematic update file ?
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
mokkami said:
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
Click to expand...
Click to collapse
I want to give it a try. Yes,however I don't have to install the update. But I think I will flash a stock rom,make the update and then re-root the phone.
Thank you guys, I was going crazy with this rebooting problem. So now it is fixed, but how can I get the update? Noway?
mokkami said:
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
Click to expand...
Click to collapse
I was able to enable the usb debugging,and then to start the bootloader. However If I connected the phone and tried to execute the adb reboot-bootloader command it didn't worked. So I restarted the phone and entered into the bootloader,then I've done the following:
fastboot reboot-bootloader
fastboot erase cache
After the first command,the phone rebooted into bootloader,then the second command finally cleared the chace. Now my uptime is more then 8 minutes,so the phone is working great now
However I will do the complete process on the weekend,but not now as I'am really tired,but I will flash a stock rom at the weekend.
Possible solution...
Just started a thread with a possible solution
http://forum.xda-developers.com/showthread.php?t=2663205
Hope it helps...