Related
excuse me for being stupid please....i have rooted my atrix before with ease but something happened tonight with rooting the Vivid...i had everything rooted completely and went to push out the VJRAIDER rom...however something went terribly wrong! the phone seems to be stuck in a boot loop. in the Hboot menu everything ends up being a boot loop, recovery does nothing...factory image does nothing....please someone give me a hand i am just lost...
What steps did you do so far? Have you flashed the kernel already? Maybe try flashing it in fastboot.
can you explain how to do what your saying. i have tried to relock the phone which worked but still stuck in the boot loop...tried to do the factory reset. how can i load the stock image on through the CDM? im decently savvy on this stuff just new to this phone...
Please refer to:
http://forum.xda-developers.com/showthread.php?t=1416836
There you will find what you need.
not sure i am understanding how i can use that information without the ability to get into my OS.....it seems i don't have an OS to boot into? or is it that something didn't finish or setup?
Wow! he have the same exact problem. Please notify me when you find a fix for this! Im trying really hard
i was just able to do the fastboot flash boot boot.img and it went through.....what should i do from this point?
nickshute91 said:
i was just able to do the fastboot flash boot boot.img and it went through.....what should i do from this point?
Click to expand...
Click to collapse
Now if your still have issue with recovery (recovery showing up for half a second then reboots) just reflash recovery from bootloader then you can start the process of flashing the ROM over.
There's an instructions post on how flash the ROM:
http://forum.xda-developers.com/showpost.php?p=21042415&postcount=4
Please read it carefully
its not coming up to recovery AT ALL....and i read that multiple times....i am not understanding it obviously and need an extra hand.
nickshute91 said:
its not coming up to recovery AT ALL....and i read that multiple times....i am not understanding it obviously and need an extra hand.
Click to expand...
Click to collapse
Reflash recovery
nickshute91 said:
its not coming up to recovery AT ALL....and i read that multiple times....i am not understanding it obviously and need an extra hand.
Click to expand...
Click to collapse
So you pulled the battery and put it back and held the volume down button.
Do you see recovery option there if not as the previous post said flash recovery using fastboot flash.....
Sent from my HTC Raider X710e using XDA App
Need serious help.
I flashed dirty unicorns and data and sms wasn't working so I tried to restore my phone but TWRP didn't see anything to restore. So desperately, i saw that it still saw my ViperRom zip so i flashed that and now I'm stuck in the splash screen. I tried to get the phone back to recovery with the toolkit and it doesn't see my phone.
TheSignor said:
Need serious help.
I flashed dirty unicorns and data and sms wasn't working so I tried to restore my phone but TWRP didn't see anything to restore. So desperately, i saw that it still saw my ViperRom zip so i flashed that and now I'm stuck in the splash screen. I tried to get the phone back to recovery with the toolkit and it doesn't see my phone.
Click to expand...
Click to collapse
more info:
I just tried the button combo light trick and was able to enter recovery. but alas I am at a loss what to do now. I still can't see my backups. I'm now doing a standard wipe and reinstalling ViperRom. Please God let this work.
update: Phone is alive.......but, i'm stuck on EVDO and Goomanager doesn't seem to see any of my original stuff. I'm aware this is the 4.2.2 thing but I am not really educated on how to deal with that.
TheSignor said:
more info:
I just tried the button combo light trick and was able to enter recovery. but alas I am at a loss what to do now. I still can't see my backups. I'm now doing a standard wipe and reinstalling ViperRom. Please God let this work.
update: Phone is alive.......but, i'm stuck on EVDO and Goomanager doesn't seem to see any of my original stuff. I'm aware this is the 4.2.2 thing but I am not really educated on how to deal with that.
Click to expand...
Click to collapse
Look here Q14
bigdaddy619 said:
Look here Q14
Click to expand...
Click to collapse
Thanks. Only one question though. I just finished copying my restore from the 0 folder and pasted it, now TWRP can see it and is finally willing to restore. Will the restore solve this issue just as easily or is it that as soon as you flash a 4.2.2 is your system forever changed without this fix? I only ask because I don't want to flash that zip and create a new issue if the restore will quite literally send me back in time to before I even flashed 4.2.2.
TheSignor said:
Thanks. Only one question though. I just finished copying my restore from the 0 folder and pasted it, now TWRP can see it and is finally willing to restore. Will the restore solve this issue just as easily or is it that as soon as you flash a 4.2.2 is your system forever changed without this fix? I only ask because I don't want to flash that zip and create a new issue if the restore will quite literally send me back in time to before I even flashed 4.2.2.
Click to expand...
Click to collapse
TBH I only use sense roms ask your question in the 4.2.2 > 4.1.2 thread
Hello, I recently unlocked my bootloader and flashed a recovery. I flashed a new ROM, TikTak 4.42. After flashing the rom from CWM it started and went to a constant blue screen.
I flashed a new recovery via fastboot and flashed the rom again, it started but when it got to the locale selection and restarted after 2 seconds. This would repeat over and over. I decided to do a wipe, but inadvertantly wiped my storage too.
I pushed another ROM to the device via adb and flashed that via CWM, same problem as the constant rebooting. I tried to flash a RUU from fastboot but got a "Signature Fail" error.
My phone has access to the bootloader and recovery. My storage is empty so I have no roms on my phone. In mounts and storage it always says "mount /system" and "mount /data". Could this be a problem with system?
If you have any questions please ask, I'm quite new to all this so may not have included everything necessary. If anyone can help me fix my phone totally, I could make a small donation thorugh paypal
Thanks in advance
SK
SteveKeith said:
Hello, I recently unlocked my bootloader and flashed a recovery. I flashed a new ROM, TikTak 4.42. After flashing the rom from CWM it started and went to a constant blue screen.
I flashed a new recovery via fastboot and flashed the rom again, it started but when it got to the locale selection and restarted after 2 seconds. This would repeat over and over. I decided to do a wipe, but inadvertantly wiped my storage too.
I pushed another ROM to the device via adb and flashed that via CWM, same problem as the constant rebooting. I tried to flash a RUU from fastboot but got a "Signature Fail" error.
My phone has access to the bootloader and recovery. My storage is empty so I have no roms on my phone. In mounts and storage it always says "mount /system" and "mount /data". Could this be a problem with system?
If you have any questions please ask, I'm quite new to all this so may not have included everything necessary. If anyone can help me fix my phone totally, I could make a small donation thorugh paypal
Thanks in advance
SK
Click to expand...
Click to collapse
You need to read and understand these two threads and then you will be able to resolve your problem
http://forum.xda-developers.com/showthread.php?t=2265618
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Both great threads and they cover all you need to know and understand
TikTak 4.42..? :laugh:
my guess is that it's cwm causing your problems, may I suggest trying twrp instead
L0rdNels0n said:
You need to read and understand these two threads and then you will be able to resolve your problem
http://forum.xda-developers.com/showthread.php?t=2265618
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Both great threads and they cover all you need to know and understand
Click to expand...
Click to collapse
Thank you both for the replies, I'll be sure to read them now, and will try TWRP.
I can't seem to find an RUU for my device, it's hutchinson 3g, uk, which has the 3 digits 771. I can't find that in any of the listed RUU's
beanbean50 said:
TikTak 4.42..? :laugh:
my guess is that it's cwm causing your problems, may I suggest trying twrp instead
Click to expand...
Click to collapse
I tried flashing the rom with twrp but have the same problem, it boots up, gets to the choose location menu and then reboots. If it's important, when I'm in the bootloader it says "OS- (blank)"
SteveKeith said:
I tried flashing the rom with twrp but have the same problem, it boots up, gets to the choose location menu and then reboots. If it's important, when I'm in the bootloader it says "OS- (blank)"
Click to expand...
Click to collapse
damn, I wish I had a good memory as someone else had the same problem about a week ago (I think it was in the viper thread) i'll try to find it for you, but don't hold your breath!...
Edit:
found it..!
hope it helps you
http://forum.xda-developers.com/showpost.php?p=48816309&postcount=23652
beanbean50 said:
damn, I wish I had a good memory as someone else had the same problem about a week ago (I think it was in the viper thread) i'll try to find it for you, but don't hold your breath!...
Edit:
found it..!
hope it helps you
http://forum.xda-developers.com/showpost.php?p=48816309&postcount=23652
Click to expand...
Click to collapse
Thank you for helping! I think I may have worded my last reply badly. My recovery works, I'm currently on twrp, and I can flash a rom. When i flash the rom, I reboot the system, goes through boot screen etc, gets to choose locale i.e UK, USA, its the normal android start up, then it just crashes and reboots
SteveKeith said:
Thank you for helping! I think I may have worded my last reply badly. My recovery works, I'm currently on twrp, and I can flash a rom. When i flash the rom, I reboot the system, goes through boot screen etc, gets to choose locale i.e UK, USA, its the normal android start up, then it just crashes and reboots
Click to expand...
Click to collapse
well, your nearly there!
it might be worth trying 'fastboot erase cache' to flush out any gremlins
beanbean50 said:
well, your nearly there!
it might be worth trying 'fastboot erase cache' to flush out any gremlins
Click to expand...
Click to collapse
I installed the stock rom, worked fine. I used the TWRP as you said and the thread from Lord Nelson. If you would PM me your paypal email I could make a small donation to say thank you
SteveKeith said:
I installed the stock rom, worked fine. I used the TWRP as you said and the thread from Lord Nelson. If you would PM me your paypal email I could make a small donation to say thank you
Click to expand...
Click to collapse
no need for that, just happy to help you out
beanbean50 said:
no need for that, just happy to help you out
Click to expand...
Click to collapse
Thank you It's much appreciated
you can also try this recovery , its bad ass! http://forum.xda-developers.com/showthread.php?t=2201860
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Sari95 said:
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Click to expand...
Click to collapse
if you are sure that you have an z1... then just remove the device check in the updater script (within the zip...) it is in the beginning... cant really remember how it looks but ... search google perhaps.. then it will flash weird enough ... my s also identifies as an sl... but that is from the build prop
HellRoot said:
if you are sure that you have an z1... then just remove the device check in the updater script (within the zip...) it is in the beginning... cant really remember how it looks but ... search google perhaps.. then it will flash weird enough ... my s also identifies as an sl... but that is from the build prop
Click to expand...
Click to collapse
Haha, yes. I google for it and tried to simply delete the device check in update-script, but it didn't work for me. I believe the issue is in my recovery, which is not a 4.4 kitkat recovery. The CWM-recovery I have at the moment is 6.0.3.6 and I believe that is the reason for my issues. I have had no luck trying to find a 4.4 kitkat recovery... any tips here?
Sari95 said:
Haha, yes. I google for it and tried to simply delete the device check in update-script, but it didn't work for me. I believe the issue is in my recovery, which is not a 4.4 kitkat recovery. The CWM-recovery I have at the moment is 6.0.3.6 and I believe that is the reason for my issues. I have had no luck trying to find a 4.4 kitkat recovery... any tips here?
Click to expand...
Click to collapse
well..i have never had problems with it being the recovery... what error does it make now?
HellRoot said:
well..i have never had problems with it being the recovery... what error does it make now?
Click to expand...
Click to collapse
I tried this recovery too, without any luck: http://forum.xda-developers.com/showthread.php?p=49966299
To begin with I got Status 7 error, which is now gone.. I found a tutorial to flash SlimRom for Z1, which is android 4.4.2: http://www.ibtimes.co.uk/android-4-4-2-kitkat-sony-xperia-z1-available-via-slimkat-rom-1432702
However, I was only able to make emergency calls, no cellular at all. I flashed CM through the same method and everything I tried worked, except cellular. Thus, I had to wipe it and install stock Sony firmware.
After that I tried flashing CM the "normal" way through recovery and everything installed as usual, but when I push reboot to reboot the system, the phone simply shuts off. Even if I press the powerbutton to turn it on, it only vibrates and nothing else happens. Again, I flashed stock firmware to be able to use the phone again...
I am very confused about this, because it does not give any errors. It simply does not work :l
[/COLOR]
Sari95 said:
I tried this recovery too, without any luck: http://forum.xda-developers.com/showthread.php?p=49966299
To begin with I got Status 7 error, which is now gone.. I found a tutorial to flash SlimRom for Z1, which is android 4.4.2: http://www.ibtimes.co.uk/android-4-4-2-kitkat-sony-xperia-z1-available-via-slimkat-rom-1432702
However, I was only able to make emergency calls, no cellular at all. I flashed CM through the same method and everything I tried worked, except cellular. Thus, I had to wipe it and install stock Sony firmware.
After that I tried flashing CM the "normal" way through recovery and everything installed as usual, but when I push reboot to reboot the system, the phone simply shuts off. Even if I press the powerbutton to turn it on, it only vibrates and nothing else happens. Again, I flashed stock firmware to be able to use the phone again...
I am very confused about this, because it does not give any errors. It simply does not work :l
Click to expand...
Click to collapse
just copied from the CM11 dev fora...
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
HellRoot said:
[/COLOR]
just copied from the CM11 dev fora...
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Hmm... seems reasonable. Could you give me the link to the fora, so I can try this method out too ?
Sari95 said:
Hmm... seems reasonable. Could you give me the link to the fora, so I can try this method out too ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2540650
there it is.... hope you figure it out.
Sari95 said:
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Click to expand...
Click to collapse
I had this problem when I try to flash with LB.
HellRoot said:
http://forum.xda-developers.com/showthread.php?t=2540650
there it is.... hope you figure it out.
Click to expand...
Click to collapse
Thank you I kind of figured it out... but I am not sure why/ how xD I wiped everything, flashed stock firmware "a.136", rooted, installed recovery and flashed CM. After that, it worked as it is supposed to, so problem solved
Thanks for your help
Sari95 said:
Thank you I kind of figured it out... but I am not sure why/ how xD I wiped everything, flashed stock firmware "a.136", rooted, installed recovery and flashed CM. After that, it worked as it is supposed to, so problem solved
Thanks for your help
Click to expand...
Click to collapse
good to hear hope you enjoy the CM.... if you want then please tell me how it is running.. performance, battery, camera etc
have a good day
ok here it goes
This is the first time i touch this Vivid, a few days ago I rooted it withou issues and has TWRP installed, i also did 2 full backups at that time just in case.
This morning i tried to install a new ROM, CyanogenMod 11 - Android 4.4.2 - KitKat. Basically the steps i took were
1. boot into twrp recovery
2. Did a factory reset
3. Did a System Reset
4. Clared cache and Dalvik cache
5. install the rom
6. install PA gapps
7. booted the phone wich got stuck in the htc screen forever
8. remembered that i was s-off and didnt flash the boot.img
9. repeated steps 1 thru 8 and after that flashed boot.img using fastboot
10. rebooted the phone but it was still getting stuck on htc screen
After all this i decided it was not worth it so i went back into twrp to restore my backup, unfortunately after restoring an booting the phone i am able to go past the htc screen, get the beats audio and att splash screen but it stays there, now stuck on att screen.
I have tried also to restore my second backup with basically the same results
any ideas or suggestions on what could i do next?
cantuluis said:
ok here it goes
This is the first time i touch this Vivid, a few days ago I rooted it withou issues and has TWRP installed, i also did 2 full backups at that time just in case.
This morning i tried to install a new ROM, CyanogenMod 11 - Android 4.4.2 - KitKat. Basically the steps i took were
1. boot into twrp recovery
2. Did a factory reset
3. Did a System Reset
4. Clared cache and Dalvik cache
5. install the rom
6. install PA gapps
7. booted the phone wich got stuck in the htc screen forever
8. remembered that i was s-off and didnt flash the boot.img
9. repeated steps 1 thru 8 and after that flashed boot.img using fastboot
10. rebooted the phone but it was still getting stuck on htc screen
After all this i decided it was not worth it so i went back into twrp to restore my backup, unfortunately after restoring an booting the phone i am able to go past the htc screen, get the beats audio and att splash screen but it stays there, now stuck on att screen.
I have tried also to restore my second backup with basically the same results
any ideas or suggestions on what could i do next?
Click to expand...
Click to collapse
Do you know if you had the original Gingerbread or had upgraded to ICS? If you were still on GB, then you should be able to run the RUU for that, if ICS there is an RUU you can install. Read all the directions carefully, most things seem easy but have pitfalls if you are not careful enough.
cmerlyn said:
Do you know if you had the original Gingerbread or had upgraded to ICS? If you were still on GB, then you should be able to run the RUU for that, if ICS there is an RUU you can install. Read all the directions carefully, most things seem easy but have pitfalls if you are not careful enough.
Click to expand...
Click to collapse
I dont know what i was running originally. However i am back in business!!!
I found the superguide followed it regarding the RUU and luckily i got my phone to work again.
I want to try flashing the CM11 again, i am guessing that either i am doing something wrong or maybe TWRP is not working correctly on my phone and not flashing the rom as it should.
Any known issues with TWRP and the vivid? shall i try another recovery?
Are the following steps pretty much what i should do to flash it
1. factory reset
2. system reset
3. clearing caches
4. flash boot.img (i am s-on)
5. flash rom
6. flash gapps
any suggestion is welcomed
Hboot version from the boorloader?
Sent from my Vivid 4G using Tapatalk
rignfool said:
Hboot version from the boorloader?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
it is 1.85.0025
additional info:
After recovering the phone i decided to lock the bootloader and start all over again. I re-root and then, instead of installing TWRP i used CWM and obviously, got a nand backup.
O tried flashing again CM11 and got the exact same results. Stuck in the initial HTC screen forever. Tried to restore my NAND Backup and the result was also exactly the same as before, phone would get the htc screen, then the beats audio and att animations and then will stuck onthe att screen forever.
This is weird, i must be doing something wrong here...
Reading thru a few times. You did indeed flash the image? fastboot flash boot boot.img on command line. Make sure boot.img was extracted from the rom to the folder you are typing that in. You do that after flashing rom and gapps. It has to be done from bootloader not recovery.
How long are you letting it sit. Had a phone that I thought was doing that, just took a few extra minutes to boot up.
"Small mistake"
Sorry for your problem, I think there was a small mistake before installing CM11, and was what you describe in step 3 "Did a System Reset" when the installation instructions say: "Wipe data, cache, and dalvik cache". I'm afraid you can only recover your VIVID through JTAG on any site that offers the service, it seems you deleted your operating system. The other option is to try [unbrick] HTC Unbricking Project By dexter93 developers forum, http://forum.xda-developers.com/showthread.php?t=1627886;
All the best. Just a recommendation, read, read and read each post and comments to take no surprises. Good luck.:fingers-crossed
I would appreciate your comments
I don't think that post is relevant. You still have access to bootloader and recovery right? Then it isn't bricked.
Yuskow said:
I don't think that post is relevant. You still have access to bootloader and recovery right? Then it isn't bricked.
Click to expand...
Click to collapse
Yes i do have access to bootlader and recovery, i actually was able to bring back to life the phone using RUU. So the issue now is not that the phone is bricked but that anything i try to load on it fails, being CM11 or even the NAND backup that i took with this same phone just after installing recovery, nothing seems to work.
I was googling around and so another person that had similar behavior on his vivid but didn't posted if he was ever able to fix it...
Yuskow said:
Reading thru a few times. You did indeed flash the image? fastboot flash boot boot.img on command line. Make sure boot.img was extracted from the rom to the folder you are typing that in. You do that after flashing rom and gapps. It has to be done from bootloader not recovery.
How long are you letting it sit. Had a phone that I thought was doing that, just took a few extra minutes to boot up.
Click to expand...
Click to collapse
Yes indeed. I used fastboot to flash the boot.img, i will try to do it again today and make sure that i do this after flashing rom and gapps. I might as well try another rom.
Anyone ROM that you recomend me to try?
You tried reading the following post: http://forum.xda-developers.com/showthread.php?t=2642575,? It's different from what I showed above, there describes another way to recover your vivid by projectisaac:fingers-crossed:
cantuluis said:
Yes indeed. I used fastboot to flash the boot.img, i will try to do it again today and make sure that i do this after flashing rom and gapps. I might as well try another rom.
Anyone ROM that you recomend me to try?
Click to expand...
Click to collapse
CM11 kicks ass. http://69.10.54.187/nightly/holiday/ is where you might find the latest nightlies.
Seems to be the only vivid rom that has been worked on for a while.
First time I tried running a custom rom I had a similar issue to what you experience. Do you happen to be on bell? After restoring with the RUU and unlocking again, all went well.
The best guide is http://forum.xda-developers.com/showthread.php?t=1416836 but just use it as a guide line and use this software instead.
http://forum.xda-developers.com/showthread.php?t=2437705
Some people say to run the fastboot command 2x. I've been following that advice. Figured it can't do anything bad.
Yuskow said:
CM11 kicks ass. http://69.10.54.187/nightly/holiday/ is where you might find the latest nightlies.
Seems to be the only vivid rom that has been worked on for a while.
First time I tried running a custom rom I had a similar issue to what you experience. Do you happen to be on bell? After restoring with the RUU and unlocking again, all went well.
The best guide is http://forum.xda-developers.com/showthread.php?t=1416836 but just use it as a guide line and use this software instead.
http://forum.xda-developers.com/showthread.php?t=2437705
Some people say to run the fastboot command 2x. I've been following that advice. Figured it can't do anything bad.
Click to expand...
Click to collapse
ok guys i am now officially an idiot.
Problem came down to be that i was using the wrong boot.img, i didnt know that the correct one is INSIDE the rom zip. I tried it once more and now i am running CM11
thanks for your suggestions and sorry for taking your time on this newb learning experience
alosegon said:
Sorry for your problem, I think there was a small mistake before installing CM11, and was what you describe in step 3 "Did a System Reset" when the installation instructions say: "Wipe data, cache, and dalvik cache". I'm afraid you can only recover your VIVID through JTAG on any site that offers the service, it seems you deleted your operating system. The other option is to try [unbrick] HTC Unbricking Project By dexter93 developers forum, http://forum.xda-developers.com/showthread.php?t=1627886;
All the best. Just a recommendation, read, read and read each post and comments to take no surprises. Good luck.:fingers-crossed
I would appreciate your comments
Click to expand...
Click to collapse
Please... Do not scare people like that...
AFAIK... You only need a JTAG if your phone reads qhusb_download... Or something like that...
I have erased my OS literally hundreds of times...
Sent from my Vivid 4G using Tapatalk
rignfool said:
Please... Do not scare people like that...
AFAIK... You only need a JTAG if your phone reads qhusb_download... Or something like that...
I have erased my OS literally hundreds of times...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
thanks for clarifying that
Glad you're up and running.
Btw, this ROM is amazing, so much better than the stock at crap
Sent from my Vivid 4G using Tapatalk