[Q] Formated /boot and phone dont inicialize - Nexus S Q&A, Help & Troubleshooting

Edit:
Hello everybody!
I formatted / boot through the Clockwordmod and now the phone does not boot the android, always turns on Clockword.
I tried to use fastboot to install a new boot, but does not work, is always "waiting for device".
What should I do? Is there any way to install a new boot using the Recovery?
Please! I'm desperate!

By /boot do you mean the bootloader? To me you seem to have removed the OS from your phone so you may have killed it.
Unless you have a bootloader I'm which case your fine.
Sent from my Nexus S using xda premium

I formated /boot. I can enter on Clockword normaly, but just it. I remove the OS, I think.
I had lost my phone??

If I use fastboot with one bootloader img, can I solve this problem?

So, I cant use fastboot. My PC doenst recognize my phone!
Anybody help?
Please, i´m very sad about it!

u might need Odin then to flash your original firmware. Make sure you download the right version for your phone.
Sent from my Nexus S 4G using xda premium

Boot into recovery go into backup and restore from a backup you made earlier. You can also just restore boot using the advanced backup restore.
If you don't have any backups and clearly you have a custom recovery installed, what can I say... serves you right.

Boot is the kernel.
Mount USB storage in clockworkmod recovery. Put a kernel on the phone and flash it.
Or flash a rom
Or restore a backup off the boot as mentioned .

Related

[Q] Soft Brick - TWRP intact, how to flash?

Okay so I sold my HOX running AOKP to a guy on Clist. He tried to flash a stock rom.. and somehow in the process wiped his whole system and sd card. Over the phone I figured out he soft bricked it and its stuck in a bootloop.
Went thru the steps over the phone with him to get into recovery(TWRP), and he confirmed that TWRP is there. Of course he didnt do a nandroid or anything of that sort, so he cant revert to that. There's no ZIPs on the phone, when he goes to INSTALL on twrp, it just shows "twrp" folder and thats it.
I haven't had the phone in my hands yet, but will see it tomorrow. My question is:
How do I transfer a Zip file onto the phone to flash thru TWRP? Does TWRP have a USB mass storage mode? (I have an S3 now and that's not available on my TWRP)
Can I use ADB or Fastboot to flash the ZIP as is? Or can I use ADB to transfer a file to the phone?
Yeah twrp has usb storage, you go into Mount then mount usb storage and windows should recognise so long as you have the correct drivers installed.
Sent from my HTC One XL using xda premium
Sweet. Ill do that tomorrow
Sent from my SAMSUNG-SGH-I747 using xda premium
Maybe I didn't understand the op but, when flashing... You'll have to flash the boot.IMG file from the rom seperately if the phone has the 1.14 Hboot. Then go into recovery and install the .zip file after you wipe the cache/delvik.
Sent from my HTC One XL using xda app-developers app
s1mpd1ddy said:
Okay so I sold my HOX running AOKP to a guy on Clist. He tried to flash a stock rom.. and somehow in the process wiped his whole system and sd card. Over the phone I figured out he soft bricked it and its stuck in a bootloop.
Went thru the steps over the phone with him to get into recovery(TWRP), and he confirmed that TWRP is there. Of course he didnt do a nandroid or anything of that sort, so he cant revert to that. There's no ZIPs on the phone, when he goes to INSTALL on twrp, it just shows "twrp" folder and thats it.
I haven't had the phone in my hands yet, but will see it tomorrow. My question is:
How do I transfer a Zip file onto the phone to flash thru TWRP? Does TWRP have a USB mass storage mode? (I have an S3 now and that's not available on my TWRP)
Can I use ADB or Fastboot to flash the ZIP as is? Or can I use ADB to transfer a file to the phone?
Click to expand...
Click to collapse
You can just mount USB storage and drag the ROM to the sdcard.
If you are on the new hboot (1.14) you will have to flash the boot.img (its inside the rom zip) first (from fastboot). then flash the ROM from recovery.

[Q] Cannot restore backup, need stock ROM or help [RESOLVED]

I was trying to restore a backup made yesterday and had an md5 mismatch. I removed the md5 keys from the file, which allowed CWM to restore /data but once it got to /system it failed,
Restoring system...
Error while restoring /system!
I've found this...
http://forum.xda-developers.com/showpost.php?p=34555560&postcount=11​but it doesn't help.
The OP says to restore via TWRP, but my system/windows is not recognizing the phone via ADB so I cannot flash TWRP using fastboot.
Are these files available for CWM at all?
Are you able to boot into fastboot by holding power+volume down at boot? If so you can flash twrp and then flash the stock backups through twrp. I have never had issues with my pc recognizing my phone in adb mode with the phone in fastboot as far as flashing recovery, boot logo, etc. I am not able to get adb to push/pull files while in fastboot. Whether or not this works may depend on if you had usb debugging enabled in developer options prior to soft-bricking your phone.
Sent from my XT897 using xda app-developers app
UnicronAlpha99 said:
Are you able to boot into fastboot by holding power+volume down at boot? If so you can flash twrp and then flash the stock backups through twrp. I have never had issues with my pc recognizing my phone in adb mode with the phone in fastboot as far as flashing recovery, boot logo, etc. I am not able to get adb to push/pull files while in fastboot. Whether or not this works may depend on if you had usb debugging enabled in developer options prior to soft-bricking your phone.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply. I can get to fastboot, I tried just kind of blindly flashing the twrp recovery image, and you're right, it worked even though 'adb devices' still didn't show it.
So I'm back on TWRP but now, after following the instructions to create the TWRP backup folder on the SD card and restoring the files provided by drakeheart77, TWRP tells me there's no OS installed when I try to reboot to the system. All the posts I read suggest flashing a new ROM but... there aren't any ROMs from what I can tell.
As I said in the OP, I tried to restore a backup and ran into the md5 mismatch error, but I didn't say that in my noob-ness, formated everything I could and lost my OS because of that (at least from what I'm deducing... still noob-ness).
Any suggestions? Thanks again!
I'm guessing the "no os" error is due to not having anything in the /data folder. Try flashing this through twrp: http://forum.xda-developers.com/showthread.php?p=32514141
It is a backup of the stock odexed rom. Put the files in the twrp/backups/serial#here/ folder and try flashing it. Assuming that gets you up and running all you have to do to is flash the stock recovery.img through fastboot to download the ota update, if you want to.
For future backups try having twrp save them to your external sd card by selecting it in the backup menu. That way if you need to wipe internal storage for any reason you will have the external backups safe and ready for use.
Sent from my XT897 using xda app-developers app
UnicronAlpha99 said:
I'm guessing the "no os" error is due to not having anything in the /data folder. Try flashing this through twrp: http://forum.xda-developers.com/showthread.php?p=32514141
It is a backup of the stock odexed rom. Put the files in the twrp/backups/serial#here/ folder and try flashing it. Assuming that gets you up and running all you have to do to is flash the stock recovery.img through fastboot to download the ota update, if you want to.
For future backups try having twrp save them to your external sd card by selecting it in the backup menu. That way if you need to wipe internal storage for any reason you will have the external backups safe and ready for use.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Wow, that worked. So relieved I don't have a large black paperweight now... lol Thank you!
No problem man, glad you got it working. That backup Rangerbry posted unbricked my phone at one point and saved me a paperweight. This really is a great phone once you accept the little quirks.
Sent from my XT897 using xda app-developers app

[Q] AT&T HTC One X Softbricked-CMmod

I believe I have bricked my phone. I was running a rooted HTC One X AT&T with an odex Jellybean/HTC Sense 4+ ROM. I wanted to test out a Cyanogenmod. Big mistake. I tried to flash it from TWRP recovery, after backing up my previous ROM, however, it was stuck in an endless boot loop. I took advice from some people online and reflashed it/ wiped caches/dalvik cache etc... When I realized it would not work unless I fastbooted it myself using USB debugging I tried to reinstall the old ROM, of course, after wiping the Cyanogenmod. Long story short there was no backup even though I backed up the phone! I now have no ROM and everything on my system is gone! My SD card folder only has a TWRP recovery and I can't install any .zip files. TWRP isn't even allowing me to mount my SD card so putting any files are out of the question. I believe, however, that usb debugging was on the whole time (is it on if on the boot loader it says fastboot usb when I plug in a USB?). Is there anyway to fix this?? I'm really screwed if I can't and please don't direct me to another thread because I need personalized help. I'm doing this on a mac by the way so anyone who knows how to use the terminal would help a lot. I can get access to windows though if needed. Just please help.
Have you tried to flash the boot.img from the zip file in fastboot?
Do you know what a brick is? When your phone does NOTHING... Similar to a brick.
What happened to you is you didn't flash the boot.img through fastboot, which caused your first problem, the bootloop..
Second thing you did incorrect was perform a factory reset in boot loader... Which completely wipes your SD card and corrupts it, and which just so happened to contain your backup no worries, easily fixable...
Download a rom on your computer. While its downloading, enter recovery and choose mount. Navigate to my computer and right click the removable storage option. Choose format. Once its done, drag rom onto phone.. Flash rom in twrp.
Extract rom on your computer, grab the boot.img and flash with fastboot.
Fastboot flash boot boot.img
Reboot phone and profit
EDIT: sorry but I hastily skimmed through your post... Those are half-assed instructions for windows, I have no clue what to do on a mac
Sent from my One X using Tapatalk 2
What he said. Toolkits are easily found too

[Q] Red Triangle, Dead Android

After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
ttakacs said:
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
Click to expand...
Click to collapse
When you flashed to stock you erased your recovery.. Reconnect to your computer and push a recovery onto your phone and you're good to go..
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
ttakacs said:
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
Click to expand...
Click to collapse
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Setting.Out said:
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Click to expand...
Click to collapse
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
ttakacs said:
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
Click to expand...
Click to collapse
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Setting.Out said:
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
ttakacs said:
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
Click to expand...
Click to collapse
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Setting.Out said:
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Click to expand...
Click to collapse
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
ttakacs said:
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
Click to expand...
Click to collapse
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Sent from my Nexus S using xda premium
Setting.Out said:
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Click to expand...
Click to collapse
I am too. Every method known to me (Odin, fastboot, adb) to flash a ROM, whether custom or stock, has failed to boot. Thanks for hanging with me on this; if you can think of solution I'll be glad to have it. Or if I solve it, I'll post here.

Stuck at bootlogo, how do I fix?

I upgraded my CWM and then loaded a new Rom to my phone. During the install I had. An issue and the phone rebooted. It will not get past the boot logo. I restarted into recovery but when it loads it just reboots. It doesn't allow me to reinstall a Rom. Can I just reinstall CWM recovery to my sd and would it boot into recovery k like normal?
Sent from my LG-D800 using XDA Free mobile app
I have backed up my Rom but recovery won't stay up for me to load the back up
Sent from my LG-D800 using XDA Free mobile app
Are you s-off?
Before upgrading cwm, I am assuming you could flash different roms.
Let me / us know what you have done so far and in what state you are now in.
Edit: I am quite rusty so I may not be able to help.
Sent from my Desire HD using Tapatalk 2
Still unable to use the phone. Yes I was s off. Yeah I've been installing roms every week for years now. I saw a post about an upgrade cwm recovery and updated. I booted into recovery like normal and installed a Rom. The install went bad and The phone gets stuck on the HTC splash screen. When I boot into recovery it opens for just a second and then the phone just reboots on itself. I Havnt been.able.to do anything to it. I'm not sure what to do.
Sent from my LG-D800 using XDA Free mobile app
If you can access the bootloader still you can flash a new (your old working) recovery with fastboot can't you?
Code:
adb reboot bootloader
Code:
fastboot devices
Code:
fastboot flash recovery FILE.IMG
replace FILE.IMG with your recovery image.
also you can extract your recovery image from your last working nandroid backup. it should be just recovery.img
The way it sounds is that your boot.img got messed up somehow. Maybe try just flashing the boot.img from that rom you last flashed? (the one that doesnt work) but I would just really go about flashing a working nandroid backup/ or recovery with fastboot.
You can restore from a backup with fastboot as well I'm pretty sure...
Anyways here's a link you should check out. https://code.google.com/p/android-roms/wiki/NANDROID_Fastboot

Categories

Resources