Database Info

[Q] boot loop

Hey I hate having to post this but im stumped. i was running cm7 nightly build 21 and wanted to flash back to stock pd15img. i followed the steps but when i went to update all it did was turn s on. now my mytouch gets to the animated MY logo and loops. i can still get to recovery and i have tried restore my backup but i still get the MY animated boot logo. any help or suggestions? thanks.

Did you revert your recovery back to stock or Clockwork 2.x instead of Clockwork 3.x that CM7 requires?

Genocaust said:
Did you revert your recovery back to stock or Clockwork 2.x instead of Clockwork 3.x that CM7 requires?
Click to expand...
Click to collapse
Yep. 2.5.1.2.. I even tried just flashing icedglacier but i still get the animated MYlogo wich continues to loop.
does the phone have to be rooted to fix this? It was prior to flashing the PD15IMG, but like i said when it was done loading the image i clicked update and it just turned s on....

okay so i just made some progress i think. i just flashed icedglacier again and this time it changed the boot logo to the icedglacier boot logo but it still loops.
on the bright side of things i was really tire of seeing the mytouch logo.

theycallmechase said:
Yep. 2.5.1.2.. I even tried just flashing icedglacier but i still get the animated MYlogo wich continues to loop.
does the phone have to be rooted to fix this? It was prior to flashing the PD15IMG, but like i said when it was done loading the image i clicked update and it just turned s on....
Click to expand...
Click to collapse
the PD15IMG is a HBoot flashed image. not via Clockwork's Recovery Manager.
What method did you follow to try and unroot your phone.
We kinda need to know what you did in order to fix it.
If you store the PD15IMG onto the root of the SD card and boot into bootloader it should automatically restore everything to a factory spec.

I unrooted my device by downloading the unroot folder and using visionary and the terminl emulator.
I didnt try to flash pd15img through clockworkmod i just put it on the root of my sd card and let the hboot do the rest once it loaded the image it gave me he update option i chose to update and when my phone came back on in hboot i saw s off and now im stuck in boot loop.
I have to get to work but if you think of anything that could help me out trhat would be awesome thanks guys for reading this in the first place
ps now if i try to load the pd15img it will load the image but there is no update opyion

theycallmechase said:
I unrooted my device by downloading the unroot folder and using visionary and the terminl emulator.
I didnt try to flash pd15img through clockworkmod i just put it on the root of my sd card and let the hboot do the rest once it loaded the image it gave me he update option i chose to update and when my phone came back on in hboot i saw s off and now im stuck in boot loop.
Click to expand...
Click to collapse
Try doing this. Esp. if you did the ./gfree deal.
http://forum.xda-developers.com/showthread.php?t=863899

I also made this mistake, I had to reflash a cm7 rom or miui, downgrade the recovery to 2.5.x (could also adb push) and from there went back to stock and rerooted and flashed ice glacier.

well im downloading sdk now. my internet is super slow.

theycallmechase said:
well im downloading sdk now. my internet is super slow.
Click to expand...
Click to collapse
you are just wanting the ADB you can download and install the drivers for just that. Takes like 5 mins to get up and running.

neidlinger said:
you are just wanting the ADB you can download and install the drivers for just that. Takes like 5 mins to get up and running.
Click to expand...
Click to collapse
cool drivers are installed. so do i just need to be hboot to use the drivers? or is there some sort a software i need?

theycallmechase said:
cool drivers are installed. so do i just need to be hboot to use the drivers? or is there some sort a software i need?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=928370&page=2

neidlinger said:
http://forum.xda-developers.com/showthread.php?t=928370&page=2
Click to expand...
Click to collapse
hahaha thanks bro, love the "(great for noobs)" in the title of the thread. will try as soon as possible.
after reading the guide i have one problem.
5. On your phone go to Settings/Applications/Development and make sure USB debugging is ON and plug it in via the usb..
any suggestions??

theycallmechase said:
hahaha thanks bro, love the "(great for noobs)" in the title of the thread. will try as soon as possible.
after reading the guide i have one problem.
5. On your phone go to Settings/Applications/Development and make sure USB debugging is ON and plug it in via the usb..
any suggestions??
Click to expand...
Click to collapse
Being that you have s=on it's going to be fairly difficult. [sidenote] i still cannot believe the PD15IMG didn't work for you [/sidenote]. but you can try and use the fastboot commands.If s=off you could load a separate recovery image and flash a ROM to get you up and running.

yeah, i knew this would happen to me. when i try to adb in it dosent show my device. i have a thing with best buy where they will mail it in to htc to have it fixed but im not sure since i modded the phone.

theycallmechase said:
yeah, i knew this would happen to me. when i try to adb in it dosent show my device. i have a thing with best buy where they will mail it in to htc to have it fixed but im not sure since i modded the phone.
Click to expand...
Click to collapse
since you are in fastboot you cannot use
adb devices
Click to expand...
Click to collapse
you have to use
.
fastboot devices
Click to expand...
Click to collapse

ok so adb devices gave me a list of devices wich was none.
fastboot devices did not do anything for me.
wait a minute.... it did show something a second time it says sh0bt602653 fastboot....

Ok, that means fastboot has detected your phone. You can flash individual system.img, recovery.img, etc directly from fastboot.

so what do i flash? what commands do i need to use.

C:\adb>fastboot -p sh0b7t602653 update update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
πmªeΩ▲K¡8|x¥►╬←ì☻²╣⌂ì╒▄╞)ⁿ‼♀÷ta in 'h↑τ‼
íTQ▬á╠4δ/l≤huä╘:ì{îC`╢r◄+m§┌╪é^EÇkm☺ªfR
⌠èc┘↕á(╚αñ-0←♫┌╗ê-UY#è°┌o◄■k┤▐╩_``╠FA∞9 ÄM°c↑Sl░LΩ¥♣⌠q╦è╬5è╖P»ìì_j↑û♦ß‼[Γ╞ö¶¡l∙K
╬@↓%$»}ÅKù⌡ΘP9♂₧▒≤☺■Wm3┴pß|*╩°φ`Dú╞▒m└√±←╓6↓A¬]W,ùa½↓εWX╗ôâ\?o\ö~y╚` ╨%█εç←╚q
¶╩♥&ò⌂M─)_5m8ù╢+'⌠y<BWδ¼
!╩X┘♫■s▐k╗wS";öPôBÇ1Yé↔è_ÿ∟╧♫â`↕á┘h▐]∟-╟;»5
▼Ç↨♥H·ò⌠ƒQ²'►╟Oç∙╗Y∟ì▲67╘%)▐∩╘kO¥▬Θî☼R∟┴¼'

Recovery

Ok, so clockwork recovery has worked without fail for 8 months...
then today i tried to reboot into recovery (using power menu, adb etc) and it just sits on the google screen.
I have reflashed a few different recovery images and locked/unlocked the loader.
I can get into recovery only after straight after flashing the recovery, by going to the bootloader and selecting reboot (not recovery)
something is balked here, any ideas?
(i would just lock the bootloader again and take it back as faulty, but when that is done, it boots straight into recovery, i assume because there is no ROM there)

Lock the bootloader then unlock it again then reflash Clockwork.
Have you tried using the modded one on the dev forums at 4.0.0.2?

yep, im afraid ive done that... any way to reinstall the bootloader itself?

slimjimwoods said:
yep, im afraid ive done that... any way to reinstall the bootloader itself?
Click to expand...
Click to collapse
Yeah you can find the images (there was a update to the bootloader in 2.3.2 or something) and go into bootloader mode and type.
fastboot flash bootloader whatever-the-bootloader-name-is.img
My bootloader is: I9020XXKA3

any chance you could point me in the right direction of the images, google is seeming fruitless...

slimjimwoods said:
any chance you could point me in the right direction of the images, google is seeming fruitless...
Click to expand...
Click to collapse
Yup, no problem. I was just looking for it. Is the KA3 bootloader the version you currently have? Because I know it was optional to update the bootloader, especially for non-stock ROM'ers.
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90

currently I have I9020XXJK1...

slimjimwoods said:
currently I have I9020XXJK1...
Click to expand...
Click to collapse
Yeah thats the older bootloader that came with the stock phone. The KA3 bootloader is the newest bootloader that was included with the 2.3.3 OTA. Just make sure you're using a I9020 model. Which you probably are since you're in the UK so you shouldn't have anything to worry about.

excellent thankyou, and im right in saying
fastboot flash boot *above file*...

slimjimwoods said:
excellent thankyou, and im right in saying
fastboot flash boot *above file*...
Click to expand...
Click to collapse
1. put bootloader.img into \android-sdk-windows\tools\
2. command prompt, cd C:\android-sdk-windows\tools\ (or where ever your SDK folder is)
3. put phone into bootloader mode if it isnt already
4. fastboot flash bootloader bootloader.img
5. reboot bootloader
6. check bootloader version
p.s. verify its MD5 hash before you fastboot it

aha! thankyou, it was flash bootloader... ok thats done, I shall try clockwork and get back to you

slimjimwoods said:
aha! thankyou, it was flash bootloader... ok thats done, I shall try clockwork and get back to you
Click to expand...
Click to collapse
good luck

clockwork is fine now, flashed CM7 nightly but it just sat on the black Google screen again... going to try something a bit more stable... thankyou for your help on this

its booted
[ROM-AOSP GRJ22][NS+NS4G] Oxygen-2.1.6,

slimjimwoods said:
its booted
[ROM-AOSP GRJ22][NS+NS4G] Oxygen-2.1.6,
Click to expand...
Click to collapse
congrats CM7 nightly should of flashed too. just have to wipe dalvik,cache,factory and it should be fine afterwards.
Oxygen is pretty nice though. I manipulated the ROM to be like Cyanogen by copying over Cyanbread. More lightweight and less bloat compared to CM7.

would that add in DSP manager?

slimjimwoods said:
would that add in DSP manager?
Click to expand...
Click to collapse
Nope. have to separately add it in, Voodoo Sound is better anyways.

That's true, but I tend to run them alongside each other, dsp doing the equalizer... (like to give the treble a boost)

slimjimwoods said:
That's true, but I tend to run them alongside each other, dsp doing the equalizer... (like to give the treble a boost)
Click to expand...
Click to collapse
Just add the app in, see what happens.

[Q] Nexus S stuck on Google logo and unlock bootloader screen

I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T

I'm having the exact same problem with a GT-i9020 so would be interested in any help on this!

May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk

RANDYRKELLY said:
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock

Highl1 said:
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Click to expand...
Click to collapse
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk

Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk

RANDYRKELLY said:
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
I'll wait for your link and instructions, it's obvious that I am doing something wrong
Thanks mate!

RANDYRKELLY said:
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
But I have stock recovery and can't copy anything to internal memory, since my phone doesn't boot

Highl1 said:
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
Click to expand...
Click to collapse
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)

surdu_petru said:
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
Click to expand...
Click to collapse
Same thing mate, I ran it, click two times in console, can't unlock the bootloader, I always get stuck on it

Trying to update the drivers for Nexus S : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
and after that try to run.bat...Good luck!

I'll try today, but my problem is that adb cannot find the device, fastboot can

I would try downloading the full OTA from this thread, rename it to update.zip (for easy typing), place it in a directory where you can run fastboot, then use the command:
Code:
fastboot update update.zip

I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>

Is the problem solved？

szk5230 said:
Is the problem solved？
Click to expand...
Click to collapse
Not so far, I'm still having trouble with the phone, and no solution so far helped

Highl1 said:
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Click to expand...
Click to collapse
Sorry my bad, haven't tried that before either...

If it bugs you the bootloader isn't unlcoked before flashing can't you just use
fastboot oem unlock
then commence with flashing your stock image?
Edit - Nevermind...I see you tried that.

any other suggestion? I'm out of ideas

I had this problem in December. I tried everything you tried without any luck so eventually took it back for warranty repair. Unfortunately I had some water damage from 9 months before so they wouldn't touch it. Luckily I got it replaced on my phone insurance but they said it couldn't repaired.
As far as I know it's a hardware fault. With CWM it looked like I could transfer files into the sd but they would disappear! I was able to use Fastboot and Odin but no joy. I had the same errors when trying to apply update using fastboot and never found answers about the "missing" files.
Sorry to come with bad news and good luck! I'm worried it'll happen to my replacement handset so keen to know if you resolve it.

[Q] Bricked/softbricked and Confused {2.20?}

So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?

wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
He probably forgot to flash boot.img in fastboot.
If you are bricked, this phone will not turn on and be listed as QHSUSB_DLOAD in windows.
edit: cwm + evita(htc one xl) = bad.
he needs TWRP

wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...

Crappyvate said:
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...
Click to expand...
Click to collapse
absolutelygrim said:
He probably forgot to flash boot.img in fastboot.
Click to expand...
Click to collapse
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?

wiiareonfire said:
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?
Click to expand...
Click to collapse
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM

First, extract boot.img onto comp. Move boot.img into adb files. Rezip Rom and transfer to sdcard. Fire up command prompt where you stored boot.img. type --> fastboot flash boot boot.img
Once successful, flash Rom IN RECOVERY. profit
Tell your FRIEND to follow posts before blindly flashing, he'd be more prepared
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium

Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium

absolutelygrim said:
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM
Click to expand...
Click to collapse
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
subarudroid said:
Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium
Click to expand...
Click to collapse
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?

wiiareonfire said:
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?
Click to expand...
Click to collapse
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1

Crappyvate said:
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1
Click to expand...
Click to collapse
Code:
C:\Android>adb reboot recovery
error: device not found
Surprisingly enough, you need to be booted into android for adb commands to work. Even the bootloader option for "recovery" gets me nowhere.
Out of nowhere, he tells me he tried to flash a rom.
Ali: the rom that i flashed hmmm.
if i sent that to you would you be able to do anything?
well, tried flashing?
Me: a download link would be preferable
but yes, i'll need that
Ali Haider: got it.
give me a few minutes.
what if the rom wasn't supported?
because i can't completely remember which of the several roms i tried to flash were the problem
Me: what do ya mean "not supported"
Ali:
like clockwork- it apparently doesn't work
Me:
gimme whichever you flashed most revently
a link
i'll need the boot.img
and if you don't know which rom, gimme a list to narrow it down
and i'll go one by one
Click to expand...
Click to collapse
TL;DR, he flashed with CWM and that's why it's screwed up.
Ladies and gents, we might be getting somewhere with this. Albeit, slowly, thanks to my friend who can't read the posts.

I think Crappyvate has the right idea here. You need to flash a proper recovery.
Sent from my One X using xda premium

subarudroid said:
I think Crappyvate has the right idea here. You need to flash a proper recovery.
Click to expand...
Click to collapse
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?

wiiareonfire said:
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?
Click to expand...
Click to collapse
What happens after flashing twrp in flashboot ? what msg do you get ?

Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?

wiiareonfire said:
Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?
Click to expand...
Click to collapse
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?

Crappyvate said:
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?
Click to expand...
Click to collapse
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?

I believe Fat32, but I may be wrong on that.
And you can use windows built in formatter.

wiiareonfire said:
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?
Click to expand...
Click to collapse
yep fat 32, dunno windows sorry...

Yup fat32. That what I did. My first hox I soft bricked as well with cwm
Sent from my One X using xda premium

I formatted with FAT32... It's still not accepting the file. TWRP crashes when the adb push command is finished. Is there something I'm missing?

Wiped N5 now NO OS! Have TWRP

Hello,
I meant to factory restore my rooted N5 and on the advanced TWRP option I chose wipe data. Now I have no OS. I'm not finding a guide on how to install the stock 4.4.2 onto my N5 using a Mac. Is there a process that shows how to do that exactly for a Mac?
thx,
Mark

Install windows on your mac using bootcamp or VMware. just use windows 7/8 trial.
Sent from my Nexus 5 using Tapatalk

+1 i think thts your best bet.. :good:
lesp4ul said:
Install windows on your mac using bootcamp or VMware. just use windows 7/8 trial.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse

eodchn said:
+1 i think thts your best bet.. :good:
Click to expand...
Click to collapse
Yes, I have VMWare and Windows 7 installed. But, what is the process to get the stock rom back onto my phone? I've got TWRP and able to get into Bootloader mode.

s1w999 said:
Yes, I have VMWare and Windows 7 installed. But, what is the process to get the stock rom back onto my phone? I've got TWRP and able to get into Bootloader mode.
Click to expand...
Click to collapse
Look in the general section and at the top is the guide you need to get sorted, good luck and dont panic you haven't killed it.

You don't have to do all that just sideload a stock rom onto the phone

lesp4ul said:
Install windows on your mac using bootcamp or VMware. just use windows 7/8 trial.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Lol
Mac is fully supported by Android tools
Sent from my Nexus 5

Jables2915 said:
You don't have to do all that just sideload a stock rom onto the phone
Click to expand...
Click to collapse
Afaik know you can`t sideload a stock image, only flash in fastboot. Correct me if i`am wrong though. OP can sideload a custom rom and from there return to stock or as @Pirateghost said just use the sdk to flash the image straight away.

gee2012 said:
Afaik know you can`t sideload a stock image, only flash in fastboot. Correct me if i`am wrong though. OP can sideload a custom rom and from there return to stock.
Click to expand...
Click to collapse
100% Correct, OP can choose to do it that way or flash stock image in fastboot there's no need to use Windows at all.

Not working
Jables2915 said:
You don't have to do all that just sideload a stock rom onto the phone
Click to expand...
Click to collapse
Well, I have the Nexus Android Toolkit for oneclick root etc. I don't believe I have USB debugging "on" and I have no OS on the phone to set it to "on". The toolkit will not install the Stock rom is downloaded because is says there's a name mismatch. I choose the option to change name etc and install anyway and it just loops with the same mismatch issue.
Really frustrating. How do I download a .zip file of the rom so I can flash it. All I get are .tgz files when I download the stock rom.
Any ideas?

s1w999 said:
Well, I have the Nexus Android Toolkit for oneclick root etc. I don't believe I have USB debugging "on" and I have no OS on the phone to set it to "on". The toolkit will not install the Stock rom is downloaded because is says there's a name mismatch. I choose the option to change name etc and install anyway and it just loops with the same mismatch issue.
Really frustrating. How do I download a .zip file of the rom so I can flash it. All I get are .tgz files when I download the stock rom.
Any ideas?
Click to expand...
Click to collapse
Just put your faith in toolkits, why don`t you post your question in the toolkits thread. Let them clean up the mess Sorry if i sound a wee harsh but i HATE toolkits, they cause more problems for uneducated users than they do good.

gee2012 said:
Afaik know you can`t sideload a stock image, only flash in fastboot. Correct me if i`am wrong though. OP can sideload a custom rom and from there return to stock or as @Pirateghost said just use the sdk to flash the image straight away.
Click to expand...
Click to collapse
there are stock roms, zipped, floating around xda now. those can be pushed to recovery and flashed.

simms22 said:
there are stock roms, zipped, floating around xda now. those can be pushed to recovery and flashed.
Click to expand...
Click to collapse
Yes i know, but OP wanted to flash back to stock and the android-sdk supports Mac computers.

gee2012 said:
Yes i know, but OP wanted to flash back to stock and the android-sdk supports Mac computers.
Click to expand...
Click to collapse
ah, i missed that :angel:

simms22 said:
there are stock roms, zipped, floating around xda now. those can be pushed to recovery and flashed.
Click to expand...
Click to collapse
I'm downloading a zip now to push/flash. It's a stock rom. Just hoping it works. Next option is I'm glad to hire someone to remote in and fix it. Let me know if you're interested.
thx

s1w999 said:
I'm downloading a zip now to push/flash. It's a stock rom. Just hoping it works. Next option is I'm glad to hire someone to remote in and fix it. Let me know if you're interested.
thx
Click to expand...
Click to collapse
Here is a tutorial for how to setup adb on Mac http://www.youtube.com/watch?v=V0MyTvgfO7s, and here is a how to use it http://forum.xda-developers.com/showthread.php?t=1917237 and restore to stock .

gee2012 said:
Here is a tutorial for how to setup adb on Mac http://www.youtube.com/watch?v=V0MyTvgfO7s, and here is a how to use it http://forum.xda-developers.com/showthread.php?t=1917237 and restore to stock .
Click to expand...
Click to collapse
Excellent, I'm headed there right now.
Thank you!

s1w999 said:
Excellent, I'm headed there right now.
Thank you!
Click to expand...
Click to collapse
OK, got that set up and ./fastboot devices shows my device serial #.
Now, as long as my USB debugging is "on" (I have no way to toggle that since I have no OS, only recovery. Does the fastboot devices command working verify that USB debugging is "on"?
Now to find instructions on how what the flash commands are.
ty

s1w999 said:
OK, got that set up and ./fastboot devices shows my device serial #.
Now, as long as my USB debugging is "on" (I have no way to toggle that since I have no OS, only recovery. Does the fastboot devices command working verify that USB debugging is "on"?
Now to find instructions on how what the flash commands are.
ty
Click to expand...
Click to collapse
Download the factory image and extract with 7-zip and find a Mac flash.all command in the fastboot folder which you can select i guess. Haven`t had a Mac ever so no xperience. Make sure you have the following img files :radio, boot, bootloader, system.img zip, cache and userdata placed in the fastboot folder.
Look here for a tutorial http://au.ibtimes.com/articles/526920/20131203/flash-factory-image-nexus-complete-stock-return.htm.

gee2012 said:
Download the factory image and extract with 7-zip and find a Mac flash.all command in the fastboot folder which you can select i guess. Haven`t had a Mac ever so no xperience. Make sure you have the following img files :radio, boot, bootloader, system.img zip, cache and userdata placed in the fastboot folder.
Look here for a tutorial http://au.ibtimes.com/articles/526920/20131203/flash-factory-image-nexus-complete-stock-return.htm.
Click to expand...
Click to collapse
Well, I've got everything in place, ./fastboot devices sees my N5 but the flash command doesn't do anything when executed.
Any ideas?
Here's what terminal shows:
Marks-Air:android tools Mark$ ./fastboot devices
0591a238002ead35 fastboot
Marks-Air:android tools Mark$ ./flash-all.sh
./flash-all.sh: line 17: fastboot: command not found
./flash-all.sh: line 18: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 21: fastboot: command not found
./flash-all.sh: line 23: fastboot: command not found
Marks-Air:android tools Mark$