[Q] Phone freezes when writing to /data - HTC Sensation

Hey Folks!
Yesterday, I wanted to install CM11 on the HTC Sensation of a friend.
This is what I did to the phone:
Unlocked bootloader using the Juopunutbear method (since HTCdev unlock was not possible)
Installed TWRP 1.7.0.0 recovery using fastboot
Did a factory reset using TWRP
At this point, the phone worked well, but the SD-Card could not be formatted anymore (maybe dead ..).
So I put CM11 + GApps on another SD-Card and booted into recovery.
Wiping (factory reset) froze formatting data, pulled battery
Installing zip froze, pulled battery
As I turned the phone on again, it only showed the HTC logo and warning symbols in the corners.
To get the phone working again, I tried to restore the stock software:
Flashing RUU the normal way - restore freezes
Extracting rom.zip from RUU and flashing zip with fastboot - restore freeze (dzdata)
Putting rom.zip as PG58IMG.zip on SD-Card and flashing using bootloader - restore freezes (userdata)
Any Ideas?
Best regards,
Simon

similicious said:
Hey Folks!
Yesterday, I wanted to install CM11 on the HTC Sensation of a friend.
This is what I did to the phone:
Unlocked bootloader using the Juopunutbear method (since HTCdev unlock was not possible)
Installed TWRP 1.7.0.0 recovery using fastboot
Did a factory reset using TWRP
At this point, the phone worked well, but the SD-Card could not be formatted anymore (maybe dead ..).
So I put CM11 + GApps on another SD-Card and booted into recovery.
Wiping (factory reset) froze formatting data, pulled battery
Installing zip froze, pulled battery
As I turned the phone on again, it only showed the HTC logo and warning symbols in the corners.
To get the phone working again, I tried to restore the stock software:
Flashing RUU the normal way - restore freezes
Extracting rom.zip from RUU and flashing zip with fastboot - restore freeze (dzdata)
Putting rom.zip as PG58IMG.zip on SD-Card and flashing using bootloader - restore freezes (userdata)
Any Ideas?
Best regards,
Simon
Click to expand...
Click to collapse
Can you still flash Recovery's? If you can try flashing 4ext recovery by madmaxx and then factory reset the device from there .
Sent from my HTC Desire S using Tapatalk

heavy_metal_man said:
Can you still flash Recovery's? If you can try flashing 4ext recovery by madmaxx and then factory reset the device from there .
Thank you, for your reply!
Okay, I was able to flash 4EXT Recovery thorugh fastboot (fastboot oem rebootRUU).
It doesn't freeze formatting /data, but it fails:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
E:format_volume: make_ext4fs failed on /dev/block/mmcblk0p23
Again, when I'm trying to restore from RUU its freezing on this screen:
Code:
(bootloader) [RUU]UZ,dzdata,0
(bootloader) [RUU]UZ,dzdata,100
(bootloader) [RUU]WP,dzdata,0
Any other thoughts on this?
Click to expand...
Click to collapse
Click to expand...
Click to collapse

i think your emmc is messed up

Related

Boot Loop without Recovery. OS gone.

Ill keep this short and sweet.
I have a HOXL 1.85 evita
Used this to get superuser and busybox. Tested positive for root with root checker.
Used this to get to unlock screen and restored my partitions to what it was previously. Rebooted into OS after to make sure phone was still rooted.
Boot into fastboot and used this to start pushing JB gapps/tg endeavoru ota 30/CWM touch to phone. Everything "successful" (no failures or permission denials). Flashed the boot.img and cleared cache
Go back into bootloader and select recovery. Recovery won't load. Stuck in bootloop with the "only for development purposes" message.
Currently trying to download the 1.85 RUU, fastboot oem lock, and then restart the whole process over. Just wanted to know if anyone could offer any advice on how to fix this before i revert everything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I had a boot loop like that I did a fast boot erase cache and it reverted me back to the kernel I had from the room flash. It fixed my boot loop and allowed me to boot into recovery. I don't know if that will help with your case but flashing boot.img is what caused my boot loop.
Sent from my HTC One X using xda app-developers app
davep1982 said:
When I had a boot loop like that I did a fast boot erase cache and it reverted me back to the kernel I had from the room flash. It fixed my boot loop and allowed me to boot into recovery. I don't know if that will help with your case but flashing boot.img is what caused my boot loop.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
i fastboot erase cache and it still goes into boot loop
EDIT--------
just flashed twrp recovery and at least i have recovery working now.
no usb mount storage though. im using twrp 2.2.0. win7 keeps asking me to format the disk
Is this what you flashed?
http://forum.xda-developers.com/showthread.php?t=1763240
You realize this is an International One X ROM? It won't work on this phone.
What amuses me is that you know you have an Evita, yet you tried to flash something that has Endeavor in the file name.
These threads never get old.
Sent from my HTC One X using xda premium
_MetalHead_ said:
What amuses me is that you know you have an Evita, yet you tried to flash something that has Endeavor in the file name.
These threads never get old.
Click to expand...
Click to collapse
At least it looks like he didn't accidentally overwrite hboot like this guy did.
wow. noob moment. for some reason i ignored it stupidly hoping it would work. anyway...sorted everything out. sd card mounts now...just had to format it on win7
theledman said:
wow. noob moment. for some reason i ignored it stupidly hoping it would work.
Click to expand...
Click to collapse
You're lucky; people have hard-bricked their phones doing that.
iElvis said:
You're lucky; people have hard-bricked their phones doing that.
Click to expand...
Click to collapse
I accidentally flashed recovery to boot portion. ie
HTML:
fastboot flash boot twrp.img
instead of
HTML:
fastboot flash recovery twrp.img
.
Then I also flashed recovery to recovery portion thinking that I can boot into recovery.
But now my phone boots and stays at twrp logo.
Even when I try to boot into recovery the same twrp logo nothing happens.
please help.
Hboot: 1.12.0000
Radio : 2.1204.135.20
HTC__001

[Q] can anyone help me with my nexus 5 errors

(first sorry for my bad english)
when i power on my lg nexus 5 it stuck in boot animation like in this pictures
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
recovery mod also error,if i try to unlock bootloader it will succeed but after a restart it come back to normal locked,and i tried to flash firmware with lg flash tool but when it reach 6% got an error user data cant erase
is there any way to bring my phone back to normal?
maneeshpjoseph92 said:
(first sorry for my bad english)
when i power on my lg nexus 5 it stuck in boot animation like in this picturesView attachment 3364557
recovery mod also errorView attachment 3364566,if i try to unlock bootloader it will succeed but after a restart it come back to normal locked,and i tried to flash firmware with lg flash tool but when it reach 6% got an error user data cant erase
is there any way to bring my phone back to normal?
Click to expand...
Click to collapse
How did you proceed to unlock the BL?
To solve your bootloop: from the stock recovery wipe cache then reboot. If needed, wipe data/factory reset but you will lose your data.
unlocked boot loader in command mode it was fine it shows unlocking yes /no option and i selected yes it shows its unlocked but after i fastboot reboots it coming back to locked status and i cant see any options in recovery its blank only icon is green android icon with an red error
when i flash firmware output is userdata erase failed after 6%
maneeshpjoseph92 said:
unlocked boot loader in command mode it was fine it shows unlocking yes /no option and i selected yes it shows its unlocked but after i fastboot reboots it coming back to locked status and i cant see any options in recovery its blank only icon is green android icon with an red error
when i flash firmware output is userdata erase failed after 6%
Click to expand...
Click to collapse
Try again with this guide: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
i got the stock recovery but when i try to data reset it shows e:system not mounted,e:data not mounted etc.. i think internal card is not mounted can i repaire it?
and still my bootloader is not unlocking permanently
nyone please help me urgently
Looks like a hardware issue.

Moto G-Boot Up Problem

Hello everyone.
PROBLEM : Not booting up to the Android lock-screen
DEVICE INFO :
Phone Model : Moto G XT 1033 Dual SIM (India)
No Root.Bootloader is UNLOCKED.No customizations.
ADB Debugging disabled (default).
Moto G XT1033(Black, 16 GB)
Using : Android Lollipop (the latest update done by OTA as part of System Update)
Upgraded : 2-3 weeks after the update was released.
Info from Motorola Device Manager
Current version:N/A
What happened:
Phone ran outta charge at 0%.
Plugged it in,on restarting,after the usual startup animation,I was greeted by a dead screen ,much to my horror.
Like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried a hard reset and several reboots.nothing worked.
I can access:
The bootloader
The recovery mode
Also put in CWM (without touch)
ADB is able to recognise the device.
P.S: My case was exactly that of @ravibhat here in this thread:http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
Initially,my bootloader was locked and everytime I tried recovery it kept saying "boot failed" ,just like in ravi's case.
I unlocked the bootloader using the Motorola website and installed CWM after reading up on it.
Tried flashing stock firmware but in vain.
Went to the service center where I was told my phone has a motherboard defect and needs to be replaced( which I do not believe).
What I want:
My phone restored to normalcy.
Losing data is not an issue.
Bootloader image:
MotoG Bootup Problem - Recovery Mode failed
i have same problem in Moto G XT1033 Dual SIM ( Android Lollipop )
i haven't done anything in phone
I want My phone restored to normalcy
@spanda12 and @M.Mostafa :
I still haven't flashed stock ROM using TWRP in the proper way since i wanted to recover my data.Will be doing this soon.
Few questions :
are you able to mount /data partition in TWRP?
are you able to successfully flash any custom recovery or only able to boot up from it?
in my case,if i flash twrp recovery using "flash" command it still loads default Android recovery but i am able to boot it up using "boot" command.
syntax example :
"mfastboot boot twrp.img" or "mfastboot boot philztouch.img" works
"mfastboot flash recovery twrp.img" or "mfastboot flash recovery philztouch.img" not working.
But here are a few steps that you could follow :
Use the .img file in this zip (attached),boot up using this and then try flashing the STOCK ROM and post the log here.
Hope you're flashing the Official XT1033 5.0.2 STOCK ROM and not something else.
Also,tell us the exact tutorial/steps you followed to flash.
I see that your bootloader is LOCKED.
I suggest you to UNLOCK it first so that flashing becomes easy.
Data MAYBE lost while doing this.
If you want to try and recover your data,refer my thread and maybe try the things i did.
Also,i suggest you open a different thread since this one is for spanda12's issue.
It'll help you document,receive specific responses and resolve your issue in a better way.
M.Mostafa said:
i have same problem in Moto G XT1033 Dual SIM ( Android Lollipop )
i haven't done anything in phone
I want My phone restored to normalcy
Click to expand...
Click to collapse

Erased Internal storage by accident- what now?

Hi, I assume there are some posts about this thing already but I've already read some and I'm still stuck >.<
So- I had TWRP 2.8.6.0 and Exodus ROM, was going to wipe data,dalvik etc in order to flash a different ROM, but by accident i wiped internal storage.
So I went into fastboot mode, connected the device to my PC (already got adb in my pc). did <fastboot oem unlock> ,pushed a ROM and Gapps, and flashed a twrp (using fastboot command to flash recovery.img).
then I used <fastboot reboot recovery>, and the phone stays @ fastboot mode, and i get this-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried manually booting into recovery and I get stuck at the 'ak kernel' screen right after booting my devices ( had AK Kernel before all this happend).
could anyone please guide me through this mess I've made?
Lidor167 said:
Hi, I assume there are some posts about this thing already but I've already read some and I'm still stuck >.<
So- I had TWRP 2.8.6.0 and Exodus ROM, was going to wipe data,dalvik etc in order to flash a different ROM, but by accident i wiped internal storage.
So I went into fastboot mode, connected the device to my PC (already got adb in my pc). did <fastboot oem unlock> ,pushed a ROM and Gapps, and flashed a twrp (using fastboot command to flash recovery.img).
then I used <fastboot reboot recovery>, and the phone stays @ fastboot mode, and i get this-
I tried manually booting into recovery and I get stuck at the 'ak kernel' screen right after booting my devices ( had AK Kernel before all this happend).
could anyone please guide me through this mess I've made?
Click to expand...
Click to collapse
If you were rooted already why did you unlock your phone again? why did you flash a recovery again. If you were rooted and wiped everything how did you accomplish that? Through recovery I assume correct? Sorry just trying to fully understand what you are doing.
If you were already rooted it should be boot into recovery then push a rom and gapps over then flash
Are you holding the right keys down to boot into recovery vol - and Power
Hope you made a backup. All you need to do is flash a ROM, though if you wiped internal you may as well return to stock.
Sent from my SGH-M919 using Tapatalk

[solved + how i solved it] the current image(boot/recovery) have been destroyed

so, i was trying to install twrp, but i made a stupid mistake, instead of fastboot flash recovery i did fastboot flash boot, now it tells me: "the current image(boot/recovery) have been destroyed", when i go into bootloader, and attack the cable (both before and after) restarts itself.
things I tried: flash the original boot (it gave "FAILED (Write to device failed (no link))", obviously before the bootloader happened) change usb cable, flash the stock rom (obviously before the bootloader happened)), redownload adb /fastboot drivers, phone drivers, and google drivers. this is all i remember trying to do, i'm desperate, could someone help me please?
update: now i can use bootloader
update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
try going into the bootloader and re-unlocking it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo
Angel1104 said:
View attachment 5798249That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo
Click to expand...
Click to collapse
I don't understand if the recovery works or not, it's a bootloop with locked bootloader and you can go into recovery or locked bootloader without accessing recovery? you are confusing me, however, if you have access to recovery download the stock rom from the recovery, if not, try to unlock the bootloader again by doing fastboot flashing unlock, then flash the stock recovery and then download the stock rom from the recovery
And how do you enter that mode without the application?
enter bootloader and do fastboot reboot recovery, in bootloader you can't perform flashing actions and many other things (bootloader locked) but some things, like reboot should work
in case you get the same error for the recovery you have to unlock the bootloader again
Can I send you a private message?
yes
Did you solve it? I'm facing the same issue.
Gamer_Mida said:
update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!
Click to expand...
Click to collapse
I am having trouble understanding what you did exactly. I am getting this same error with a Xiaomi Mi 8 Lite.
Edit: got it working by disconnecting all usb ports and trying another port.
Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
same as me i dont know what to do

Categories

Resources