the issue is that was flashing the rom slim bean and gave the error then restart the recovery and now fails to mount system, data, cache etc and does not allow me to flash nor recovery nor rsd also did nothing for AHD and tools
kitkat2014 said:
the issue is that was flashing the rom slim bean and gave the error then restart the recovery and now fails to mount system, data, cache etc and does not allow me to flash nor recovery nor rsd also did nothing for AHD and tools
Click to expand...
Click to collapse
I would suggest to RSD back to stock if you haven't already tried, that's usually where I start lol.
Related
This concerns my galaxy note n7000. I had a rooted checkrom v4 working on my note. I tried to install criskelorom v2 and got bootloops. I then tried to go back to stock via odin and flashed stock N7000 KL3 ROM which i had earlier used, I had to go to stock because after bootloop even recovery was not working. now after flashing stock i am getting a strange problem of the phone getting stuck at the welcome to gt-n7000 screen . "touch the android to begin" . nothing is happening after touching the android on the screen although i can change the language etc and even the pull down notification is also working but the phone is stuck at the initial stage. I have a nandroid backup of my initial checkrom in my internal sd card but cannot restore it before installing a rom with root and cwm. Kindly help . Thanks.
I'm having the exact problem. I'm hoping we can create a soft brick sticky thread. I walked away from my phone last night because I was getting frustrated.
My attempts to flash stock ROM via Odin resulted in the "not responding" message in windows. I can get to both CWM and download mode, however any ROM flashed via CWM results in the behavior described by the OP. fortunately I have access to another Samsung phone, so I can double check driver installation (although it worked for flashing previously).
I'm continuing a search through the forums to find some alternate methods for unbricking. Hope someone has an idea.
Thanks!
It seems that the stock roms i was trying to flash were nonwipe ones so i flashed xxla3 which is a wipe rom and was able to boot . I then flashed the earlier kl3 rom over this rom because kl3 is rootable. I then rooted and installed cwm booted into recovery and restored my earlier nandroid backup. I think the situation arises because the nonwipe rom was unable to clear the cache , user data etc
Thank you for the information. I had exactly the same problem. What did you use to root KL3 ?
Just wipe both cash and user data, and reboot.
reboot to recovery mode -> mount and storage -> format system, format cache, format data.
and do a factory reset and wipe cache.
problem should be solved cause that's what i did
Flo1389 said:
Just wipe both cash and user data, and reboot.
Click to expand...
Click to collapse
Thanks
liewkingyan said:
reboot to recovery mode -> mount and storage -> format system, format cache, format data.
And do a factory reset and wipe cache.
Problem should be solved cause that's what i did
Click to expand...
Click to collapse
daaamnnn!!! I'm scared to dead because of this!! Thanks dude!!!, no more **** ass ics
I had an issue like this once or twice.
http://www.youtube.com/watch?v=L5XjF6sPef4
This skips the that screen. then I cleared some things like google framework and it all was peachy
But its not wroking for me
Hi all,
Got a strange problem.. I'm using Nik project x v4.1 with .11 radio...today i got poor network signal, so I flashed radio again n it's working fine.
Then I planned to flash xcs kernel 2.2 and faceunlock for this Rom.
When I am recovery, I got message like. "You are in safe mode, please wipe cache. If u flashed hboot.img then format system"
I took nandroid and
1. fixed permission
2. Wiped cache
3. Format system
4. Flashed both zip files
When everything got over and upon clucking power menu->reboot got alert
"You are In safe mode. Unable to access system partitions. Please format system partition except sd. Reboot in recovery. Yes or no"
I clicked no and followed steps to install new Rom (wipe data factory, wipe cache n dalvik, format system, format partition except sd )restored my nandroid backup and again got same message that
"You are In safe mode. Unable to access system partitions. Please format system partition except sd. Reboot in recovery. Yes or no"
Please help me. Worrying that my mobile will be bricked. Please guide me to get rid off this..
Edit: I clicked reboot and my mobile booted normally. But under power menu, on clicking reboot, got into same problem. Please help me to avoid this. Worry something wrong in my mobile!!
Cyb0rgz said:
Hi all,
Got a strange problem.. I'm using Nik project x v4.1 with .11 radio...today i got poor network signal, so I flashed radio again n it's working fine.
Then I planned to flash xcs kernel 2.2 and faceunlock for this Rom.
When I am recovery, I got message like. "You are in safe mode, please wipe cache. If u flashed hboot.img then format system"
I took nandroid and
1. fixed permission
2. Wiped cache
3. Format system
4. Flashed both zip files
When everything got over and upon clucking power menu->reboot got alert
"You are In safe mode. Unable to access system partitions. Please format system partition except sd. Reboot in recovery. Yes or no"
I clicked no and followed steps to install new Rom (wipe data factory, wipe cache n dalvik, format system, format partition except sd )restored my nandroid backup and again got same message that
"You are In safe mode. Unable to access system partitions. Please format system partition except sd. Reboot in recovery. Yes or no"
Please help me. Worrying that my mobile will be bricked. Please guide me to get rid off this..
Edit: I clicked reboot and my mobile booted normally. But under power menu, on clicking reboot, got into same problem. Please help me to avoid this. Worry something wrong in my mobile!!
Click to expand...
Click to collapse
When you formatted the /system partition, you wiped out Nik's ROM and then you only flashed a new kernel and a patch. That is why it you get the Unable to access system partitions.
You need to flash Nik's ROM again, then flash the kernel and then flash the patch.
tpbklake said:
When you formatted the /system partition, you wiped out Nik's ROM and then you only flashed a new kernel and a patch. That is why it you get the Unable to access system partitions.
You need to flash Nik's ROM again, then flash the kernel and then flash the patch.
Click to expand...
Click to collapse
Thanks tpbklake. Before formatting systems partition, I have taken nandroid backup. I restored nandroid but after that too, I got same alert.
Ok, I'll start from beginning. After flashing Nik Rom again, can I restore data.img from my nandroid.?
When I am recovery, I got message like. "You are in safe mode, please wipe cache. If u flashed hboot.img then format system"
Click to expand...
Click to collapse
Do you have any idea on this? I got this before flashing anything.
Cyb0rgz said:
Thanks tpbklake. Before formatting systems partition, I have taken nandroid backup. I restored nandroid but after that too, I got same alert.
Ok, I'll start from beginning. After flashing Nik Rom again, can I restore data.img from my nandroid.?
Do you have any idea on this? I got this before flashing anything.
Click to expand...
Click to collapse
You changed the radio. Either gb -> ics or ics -> gb and this causes some change in the partition layout that's why recovery is asking you to format. What I don't understand is why you didn't just format the cache partition like it told you to. It would have saved us all some time.
Nonverbose said:
You changed the radio. Either gb -> ics or ics -> gb and this causes some change in the partition layout that's why recovery is asking you to format. What I don't understand is why you didn't just format the cache partition like it told you to. It would have saved us all some time.
Click to expand...
Click to collapse
I haven't changed the radio of two different versions. Earlier I was in ICS radio .11M and again flashed the same ICS radio..11M) Yes, I did cache format as well as instructed.
While flashing radio which supports same OS version, am I need to wipe cache or its not required?
Cyb0rgz said:
I haven't changed the radio of two different versions. Earlier I was in ICS radio .11M and again flashed the same ICS radio..11M) Yes, I did cache format as well as instructed.
While flashing radio which supports same OS version, am I need to wipe cache or its not required?
Click to expand...
Click to collapse
If that's what the recovery is telling you to do, I would be inclined to agree.
I have an S5830D that I flash an CM7 rom to (APOCALYPSE-FINAL), I'm now looking at getting back to stock. I'm having trouble getting my CWM restore back. Now after doing some searching I realized I would need to flash a stock firmware version through odin. I went out and found what i believe is the correct firmware version for this Koodo model (the name is S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar.md5) and tried to flash it.
Everything in odin goes through fine up to the point where it restarts the phone, Ill attach a screenshot of what shows up for me. After the screen shows up is when I get stuck in a bootloop where the phone model shows, then the koodo bootanimation shows followed by the samsung logo. I should note though I still have complete access to recovery, the downloader mode, and even the CM rom when i restore that backup. The fact I have access to all those gives me hope as I'm sure this could be reversed.
Any advice on how I can restore this phone to stock would be greatly appreciated. I'm not very familiar with samsung devices so please try to be patient with me as I realize I have gotten into something over my head.
PS Sorry about the glare on the image its the best I could do as it disappears quickly.
Jeklund said:
I have an S5830D that I flash an CM7 rom to (APOCALYPSE-FINAL), I'm now looking at getting back to stock. I'm having trouble getting my CWM restore back. Now after doing some searching I realized I would need to flash a stock firmware version through odin. I went out and found what i believe is the correct firmware version for this Koodo model (the name is S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar.md5) and tried to flash it.
Everything in odin goes through fine up to the point where it restarts the phone, Ill attach a screenshot of what shows up for me. After the screen shows up is when I get stuck in a bootloop where the phone model shows, then the koodo bootanimation shows followed by the samsung logo. I should note though I still have complete access to recovery, the downloader mode, and even the CM rom when i restore that backup. The fact I have access to all those gives me hope as I'm sure this could be reversed.
Any advice on how I can restore this phone to stock would be greatly appreciated. I'm not very familiar with samsung devices so please try to be patient with me as I realize I have gotten into something over my head.
PS Sorry about the glare on the image its the best I could do as it disappears quickly.
Click to expand...
Click to collapse
If you have complete access to recovery mode, try wiping data and cache after flashing with Odin. That does the trick for me when I have a bootloop after flashing with Odin.
ImSoBored said:
If you have complete access to recovery mode, try wiping data and cache after flashing with Odin. That does the trick for me when I have a bootloop after flashing with Odin.
Click to expand...
Click to collapse
Agreed... reboot into recovery and clear cache and dalvik cache and then reboot.
So I've just completed a new flash with odin, I went in and flashed cwm then proceeded to factory reset, wipe cache, wipe dalvik, and I even do battery reset. Every wipe goes fine except for when I attempt to do the factory reset I received the following error:
Code:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Even after those wipes it still bootloops but thats most likely as the factory reset didn't work.
Jeklund said:
So I've just completed a new flash with odin, I went in and flashed cwm then proceeded to factory reset, wipe cache, wipe dalvik, and I even do battery reset. Every wipe goes fine except for when I attempt to do the factory reset I received the following error:
Code:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Even after those wipes it still bootloops but thats most likely as the factory reset didn't work.
Click to expand...
Click to collapse
Try not using CWM, or your SD card may be corrupt and you have to format it, I'm not sure though.
ImSoBored said:
Try not using CWM, or your SD card may be corrupt and you have to format it, I'm not sure though.
Click to expand...
Click to collapse
That did it, for some reason I had this thought in my head I had to flash cwm right away and clear stuff that way. Once odin finished I went in recovery and wiped data and cache through the stock recovery and it booted right up. Thanks for the help really appreciate it.
So, i rooted the device with thew toolkit, and installed CWM 6.0.2.5.
I have now tried to flash temastek CM 10.1 rom, but after the flashing is done, the phone goes in to S/W update mode, and boots up again with stock rom!
I have tried wipe factory reset,wipe cache and wipe dalvik cache aswell as format system! It always start the S/W update, and restoring my phone to default rom, but i still have root access.
Am i doing anything wrong! I am pretty familiar to rooting and flashing roms, but i have no idea what to do now! The phone resets itself all the time!
Thank you for your help!
Playron
Playron said:
So, i rooted the device with thew toolkit, and installed CWM 6.0.2.5.
I have now tried to flash temastek CM 10.1 rom, but after the flashing is done, the phone goes in to S/W update mode, and boots up again with stock rom!
I have tried wipe factory reset,wipe cache and wipe dalvik cache aswell as format system! It always start the S/W update, and restoring my phone to default rom, but i still have root access.
Am i doing anything wrong! I am pretty familiar to rooting and flashing roms, but i have no idea what to do now! The phone resets itself all the time!
Thank you for your help!
Playron
Click to expand...
Click to collapse
just do complete restore with the AIOT......
nvflash the device and start fresh.....
use TWRP which is much better and works perfect....
format partitions and after that fix permissions .. hit thanks if i helped
Sent from my Micromax A110 using xda premium
Hallo together,
I seem to have done something wrong while trying to flash the rom "RazRi_JB_X-2014-Jul-16".
Here is what i did:
- Unlocked to bootloader using official Motorola homepage
- Flashed CWM (non-touch) recovery using "Recovery Flasher by LeBobo v1.7", USB-Debugging was on
- Rebooted into bootloader and flashed "RAZRiRoot2" to prevent Stock-ROM from overwriting the recovery
- Tried to install the Custom ROM using CWM, but it fails to wipe cache (stuck on line "Formatting /cache")
Because it didn't work, i tried to reset everything as it was before to be able to try again - flashed stock-recovery using the Recovery Flasher by LeBobo, booted into bootloader and selected "Factory". The cell is now just showing the "Warning bootloader unlocked" warning and nothing else happens.
When i try to select the recovery in the bootloader menu, an image of a Android laying on its back with an opened hatch and a red warning symbol showing a "!" appears and nothing else happens.
I seem to have bricked my device, because i cant't really do anything now - is there any solution?
I read through different topics but could not find a real solution to this particular problem...
Thank you so much in advance for your help!
It's not bricked
At the moment u enter stock recovery with that android and red warning sy,bol, u need to press bot volume up + downp. Than it will enter stock recovery mode.
Those are the following things u can do to get custom rom,
1. Flash another recovery, cwm touch, cwm non-touch, twrp. They all work a little different.
2. Flash the custom rom and wipe everything, The wip can take some time. sometimes it will be seconds, sometimes it will take a couple of minutes. Every recovery behaves different, and every flash/wipe too.
3. enjoy
If u really want to go back to stock, flash your stock JB firmware by RSD-Lite.
Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?
StarGeneral said:
Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?
Click to expand...
Click to collapse
5 minutes is a bit too much. But that's the problem with this device. Every device behaves different and we haven't found out a solution too it.
At the moment i can't do much for you. I can only say try to wipe the partitions mannualy. Wipe system, data and cache. and mount system. And then try to install it. Maybe if that doesnt do the trick try again another recovery.
This from KTR-ROM
Code:
- Enter in TWRP or CWM
- Wipes required: data, system, cache y dalvik
*In CWM mount system must format before (Mount and storage -> Mount system)
Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!
StarGeneral said:
Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!
Click to expand...
Click to collapse
nice, glad that it worked