[Q] Razr i - no possibility to flash custom rom or stock - bricked? - RAZR i Q&A, Help & Troubleshooting

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

Related

Please help! Galaxy S plus I9001 stuck booting into recovery *Fixed* :)

Hi folks,
I tried updating my S plus to ICS today by following the instructions listed here:
theandroidsoul.com/galaxy-s-plus-i9001-ice-cream-sandwich-update-install-cyanogenmod-9-cm9-pretty-good-and-working-rom
I read through the instructions and it looked pretty simple. I successfully installed Team Win recovery, performed a backup, wiped, and then installed the CM9 rom.
After the installation, the phone just boots back into Team Win recovery. I tried reverting to the backup, but it still just boots to recovery every time.
Now that I'm stuck in TeamWin recovery, I'm at a loss on what to try next .
Does anyone have any insight on how I can fix the problem?
Thanks,
Evan
Sometimes when you flash new Recovery (usually when replacing stock recovery with modified recovery for the first time) you get stuck at bootloop. It means /boot partition was damaged. After flashing TWRP did you restart your phone and it booted correctly, or did you install everything (TWRP, got backup, wipe and install new ROM) at once?
There is a guide for i9001 bootloops
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Boot-loop
divibyzero said:
Sometimes when you flash new Recovery (usually when replacing stock recovery with modified recovery for the first time) you get stuck at bootloop. It means /boot partition was damaged. After flashing TWRP did you restart your phone and it booted correctly, or did you install everything (TWRP, got backup, wipe and install new ROM) at once?
There is a guide for i9001 bootloops
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Boot-loop
Click to expand...
Click to collapse
So is reflashing in Odin what you are suggesting? Sorry if I'm misunderstanding.
And yes, after I flashed TWRP it booted fine, the 2nd time I went into recovery, performed the backup, wiped, then flashed the rom. I've tried wiping both the cache's with no success. I've also tried reflashing the rom, wiping the cache's, restoring with the backup, wiping cache's again... nothing seems to be working
What would be different if I had installed everything (TWRP, backup, wipe, rom) at the same time?
*Edit* Reflashed through Odin and it worked great! Thanks for the help, I'm a little scared to start messing with the phone again, but ICS is tempting...
Got the rom working with a fresh backup after fixing the bootloop. Thanks again for the link divibyzero, the troubleshooting steps solved the problem, whatever it was, and now its running ICS
These Samsungs S+'s seem to be a little more finiky than my HTC.
I am still stuck in CWM Recovery mod ! When I start Download mode, I dont have ODIN option ..only Download mod start screen! Can anybody help me?
Dapper SRB said:
I am still stuck in CWM Recovery mod ! When I start Download mode, I dont have ODIN option ..only Download mod start screen! Can anybody help me?
Click to expand...
Click to collapse
What do you mean by "don't have ODIN option"?
Is bootloader.tar which used to repair bootloop problem usable on ICS roms for SGS+??
alireza7991 said:
Is bootloader.tar which used to repair bootloop problem usable on ICS roms for SGS+??
Click to expand...
Click to collapse
yup, you can use bootloader or http://forum.xda-developers.com/showpost.php?p=32655216&postcount=17 CWM with AriesVe.ops
evan8683 said:
Hi folks,
I tried updating my S plus to ICS today by following the instructions listed here:
theandroidsoul.com/galaxy-s-plus-i9001-ice-cream-sandwich-update-install-cyanogenmod-9-cm9-pretty-good-and-working-rom
I read through the instructions and it looked pretty simple. I successfully installed Team Win recovery, performed a backup, wiped, and then installed the CM9 rom.
After the installation, the phone just boots back into Team Win recovery. I tried reverting to the backup, but it still just boots to recovery every time.
Now that I'm stuck in TeamWin recovery, I'm at a loss on what to try next .
Does anyone have any insight on how I can fix the problem?
Thanks,
Evan
Click to expand...
Click to collapse
Hello guys,
I think have the same problem, this morning I installed the Team Win recovery and after a reboot my phone come into recovery mode and even after a furthr reboot I'm blocked in a bootloop that leads me always on Team Win recovery.
I tried to wipe cache, dalvik cache, factory reset and even a wipe of the system but nothing happen.
I reinstalled rom but without success.
There is a way to fix this through adb?
Advanced thanks for help
Max.
krisslake said:
Hello guys,
I think have the same problem, this morning I installed the Team Win recovery and after a reboot my phone come into recovery mode and even after a furthr reboot I'm blocked in a bootloop that leads me always on Team Win recovery.
I tried to wipe cache, dalvik cache, factory reset and even a wipe of the system but nothing happen.
I reinstalled rom but without success.
There is a way to fix this through adb?
Advanced thanks for help
Max.
Click to expand...
Click to collapse
You didn't specify, so I'll assume you have an i9001, if this is not the case, you probably shouldn't follow these instructions
Just reflash the bootloader as explained here (http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330) and you'll be fine. I had the exact same problem when I had installed CWM on my own device. It's not with adb, but it's not like you have to do a lot of effort to get Odin or anything and it will fix your device.
Marshian said:
You didn't specify, so I'll assume you have an i9001, if this is not the case, you probably shouldn't follow these instructions
Just reflash the bootloader as explained here (http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330) and you'll be fine. I had the exact same problem when I had installed CWM on my own device. It's not with adb, but it's not like you have to do a lot of effort to get Odin or anything and it will fix your device.
Click to expand...
Click to collapse
Luckily I found a windows system
Istructions you report was perfect for my case...seem I solved my problem...thanks again.
There is some i need to do for report I solved my problem ?
Bye Max.
[Boot-Loop] Can I use dd to flash bootloader?
Guys, has anyone tried to use dd to flash bootloader partition?
I assume dd if=boot.img of=/dev/block/mmcblk0p8 bs=512 should work
Can somebody attach boot.img taken with dd so I could test?
error - can t acces system csc/cnx/system
hello. I have a problem. I had installed on the phone cm10. Now I switched to cm 9 but since we locked in botloader and I returned with odin. recowery mode now you did not have the option install from sd / card only update. My problem is that now go phone but I can not install gapps. ie install it says the installation is complete, restart give when I see me many times with yellow writing including my error appears so: can t access system csc / CNX / system. and after I start the application from google. to say you've tried many variations and if you try recovery-clockwork-5.5.0.4-phone crashes every time. Please help ... (I tried many variations of gapps). thanks in advance.back with another caveat: any clockwork I try to install say installation aborted. and in the recovery mode screen down to write I / / / status = 0 / / /
evan8683 said:
So is reflashing in Odin what you are suggesting? Sorry if I'm misunderstanding.
And yes, after I flashed TWRP it booted fine, the 2nd time I went into recovery, performed the backup, wiped, then flashed the rom. I've tried wiping both the cache's with no success. I've also tried reflashing the rom, wiping the cache's, restoring with the backup, wiping cache's again... nothing seems to be working
What would be different if I had installed everything (TWRP, backup, wipe, rom) at the same time?
*Edit* Reflashed through Odin and it worked great! Thanks for the help, I'm a little scared to start messing with the phone again, but ICS is tempting...
Click to expand...
Click to collapse
Hi Evan which release of Odin did you use I am also facing the same problem for the past 28 hours and not been able to resolve it. The problem is thay the Com Port does not pop up basically the phone is not being recognised by the computer.
Please help.
sunbaj said:
The problem is thay the Com Port does not pop up basically the phone is not being recognised by the computer. Please help.
Click to expand...
Click to collapse
You must properly install Samsung mobile drivers on your PC, kill Samsung Kies process (or even better: uninstall Kies) and enable USB debugging on your phone. Then it will work.
tetakpatak said:
You must properly install Samsung mobile drivers on your PC, kill Samsung Kies process (or even better: uninstall Kies) and enable USB debugging on your phone. Then it will work.
Click to expand...
Click to collapse
The problem was that I was using Windows 8. I was able to resolve the issue after doing it on Windows XP.

[SOLVED] Am I bricked? PLEASE help me :(

Hi guys. I'm quite a noob, but have a good experience on flashing without be bricked (CM9, CM10, Crash, Paranoid...), but I have a problem.
I will explain to you step-by-step what I've done with my Note, so I wish some of you could help me.
1) I was running JB Crash ROM with PhilZ kernel.
2) Some apps got Force Close too often, so I went on Rom Manager and, after a look into the "Fix permissions" description ("It will fix some force closes" or something like that), I decided to give it a try and I tapped on it.
3) After that, my homescreen became unusable, because "TouchWiz Home" got EVERY TIME force closed without reason. Everything else worked fine, so I deciced to boot into CWM recovery to restore a nandroid backup of the same ROM.
4) Instead of tapping "restore", I tapped "backup" (my fault) and it started without possibility of get back. I got something like 200 Mb of free space, so in every case it will never have had success. My Note stucked at this point, so I decided to reboot manually (vol up+home+power) into recovery. Finally I tried to "restore" but I get this message: "ERROR WHILE RESTORING /SYSTEM".
5) I tried to reboot my Note, but it stucks at "Samsung Galaxy Note GT-N7000" screen without going on.
The good news is that it can go without problems into recovery and into download mode. What can I do? Flashing from CWM, for example, CM9 can fix this?
Please help me thanks!
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
friedje said:
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
Click to expand...
Click to collapse
After formatting /system, can I try to restore my nandroid backup? Or I have to necessary reflash my ROM? In that case, it's the same thing make it via CWM or via ODIN PC? I'm still on PhilZ recovery, which is safe I guess!
Anyway, thanks for your help
Via CWM or Odin, depends if you have your rom in the zip or the md5.tar format.
I would reflash to be clean. It's a bit more work in restoring your apps and data
afterwards, but at least you don't restore any messed up files.
if you can still access CMW and Download Mode then you probably are not brick... try fresh install through pc odin.. safe method no need to worry about bricking by fullwiping on unsafe kernel or raising triagle or binary counter whatsoever.. if you wanna play safe then PC ODIN and after that you can root your rom
Thank you guys, now I'm on stock ICS flashed via PC Odin and everything works fine I knew I was 99% not-bricked (still recovery and download mode avaiable), but I was a little scared too.
Thank you again!
glad you solved it.. :good:

cwm recovery bootloop

Phone goes to cwm recovery everytime phone boots, I can't get out of it. Did factory reset, cache erase and dalvik cache erase in cwm, it did not help. Restored backup in cwm, it did not help. I also can't mount external_sd (I wasn't able to do it before too). Cwm recovery shows "can't mount /external_sd/". So I guess I can't use my sd card to transfer files to phone. What else can I try?
Flash to stock?
Do you advise to flash to stock or are you asking if I was flashing stock? If first, I can't flash cause it's not in fastboot mode while it's in recovery, if second then yes, I was flashing to stock when bootloop occured. I forgot to wipe before flashing, so I guess that's why bootloop occured, but this is weird that it bootloops into recovery.
Try this: format system in cwm. Install new ROM in cwm and reboot.
I have the feeling the your system partition is corrupt. As a safety measure the phone boots in recovery mode.
Sent from my GT-P5110 using XDA Premium HD app
I formated /system, then set up recovery of backup. It was restoring backup, but in the process I walked off and when I returned, phone was powered off with only green led on. I guess it ran out of power because it was already low before. Now green light is on when it's plugged to charger but it does not seem to be charging as it is charging now 5 hours and nothing changed. LED lights off when I unplug it off the charger, when I plug it in back, phone vibrates 2x, led powers on and then nothing.
Ok so from time to time it still boots into recovery mode (it's mysterious when, but it lasts only few minutes, then reboots itself and returns to "black" state). I was able to do recovery of my backup, but after it turned off same thing happened so it did not help. I think I would need factory cable.
What did u do before u got this problem. What was your last action?
BTW, if u o something with your mobile, like doing something with the recovery or flashing stuff, always make Sir u have enough battery or it is connected on the net. Sometimes a bad flash can damage stuff.
Sent from my XT890 using xda app-developers app
I did not have charger with me and charging with USB takes too long so I thought it's ok to flash it as long as it's plugged in pc during flash.
Ok, I downgraded from JB to ICS stock. Yes yes I know, but let me finish. I never accepted OTA update and I made SURE to delete lines in xml where is motoboot and userdata (as omar advised) and gpt (as HSD-Pilot advised). It looked good. I forgot to wipe before though, so I knew that's why classic bootloop occured (showing motorola logo, intel logo, reboot, repeat). I didn't worry about it much though as this is frequent problem and has many solutions. I couldn't simply go to fastboot mode, so I wanted to know if there is available adb during any phase of fastboot. So I did "adb wait-for-device". When I did this, it went to recovery mode and from then on I could not exit it. You are surely asking how is it possible that this adb command caused this. Well, I have no idea either, but that is what happened.
Then I couldn't power off phone, because it restarted itself at every try to power it off into cwm recovery (I willnever buy phone with unplugable battery again). So I at least left plugged it into pc during night. If it was loosing power during night and battery was charged more before, I don't think it would help - because it would eventually still loose it all. In morning it worked same, for a few hours I guess, then it added black screen with green light into its mysterious behaviour repertoire . But as I said, it still boots itself into cwm recovery from time to time, thing is I am out of ideas what to do there.
In recovery mode u can use adb to boot in boot loader. Or to shut the phone down with a command. Try it and see if it works.
U can also try to flash a boot.IMG by cwm or fast boot(boot loader) if u can get there. Flash by cwm can be done with adb side load if the external SD doesn't work.
Sent from my GT-P5110 using XDA Premium HD app
No I can't where do you get these assumptions? You can't use adb nor fastboot while in recovery mode. And in my case with cwm 6.0.1.9 it also does not detect external sdcard and adb also does not catch in sideload, I suspect this version is faulty, I have no idea why it's propagated in this xda forum section.
Once again:
-stuck in recovery
-cant use adb
-cant use fastboot
-cant use sideload
-cant use sdcard
Sorry maybe I miss read your story. I thought u tried Adb in boot loader when it all goes wrong. But u already stated it.
The only thing is, I can't get my head around your problem. Adb should work in cwm always. It is like a part of it. This is as far as my knowledge about the phone goes. U already tried the hard-reset (power, up-volume,down-volume,camera buttons).
I only have one more thing. If u do the hard-reset. Release alle buttons except the volume-down button when it reboots. Like the booting sequence for booting in boot loader. Sometimes u need to do this when the power cable is out and sometimes when it is on the phone.
If u already have done this or it also won't work after some trying than I don't know anymore. Maybe someone with more experience can help u or u can try to get support form Motorola.
Please help!
I have problems with the installation. I did full wipe in CWM.
Wipe data / factory reset
wipe Cache
Wipe cache Dalvick
Format Sytem
Format cache
Format Panic (panic error in CWM mount)
Format PDS
Now every time I try to install rom infinite boot loop
I can only install with rom instal bat.
Flash zip error after full wipe
How to solve this error?
I have already installed SML 29 via RSD_LITE to try to solve, but the error appears again when I install flash zip rom
Forgive my bad english
If u are using cwm 6... Try the first cwm one. Cwmalpha. Or try twrp the latest one. If all doesn't work use fast boot (bat file one) to get to stock.
But where have u read to format PDS and panic? Why would u do it and need it? Not that they cause the bootloop I think.
Sent from my XT890 using xda app-developers app
I've somewhat had this problem on my Atrix. Check and see if it helps.
http://forum.xda-developers.com/showthread.php?t=1131649
http://forum.xda-developers.com/showthread.php?t=1575035
DinizZ said:
Please help!
I have problems with the installation. I did full wipe in CWM.
Wipe data / factory reset
wipe Cache
Wipe cache Dalvick
Format Sytem
Format cache
Format Panic (panic error in CWM mount)
Format PDS
Now every time I try to install rom infinite boot loop
I can only install with rom instal bat.
Flash zip error after full wipe
How to solve this error?
I have already installed SML 29 via RSD_LITE to try to solve, but the error appears again when I install flash zip rom
Forgive my bad english
Click to expand...
Click to collapse
I have the same problem like you, i did exactly like you and cant install any custom rom, only rsd flash.
Can you fix it?
Thanks
Hazou said:
If u are using cwm 6... Try the first cwm one. Cwmalpha. Or try twrp the latest one. If all doesn't work use fast boot (bat file one) to get to stock.
But where have u read to format PDS and panic? Why would u do it and need it? Not that they cause the bootloop I think.
Sent from my XT890 using xda app-developers app
Click to expand...
Click to collapse
Panic / PDS clean just out of curiosity. After this procedure does not install flash rom zip, red logo Motorola start and restart forever.
CWM-based Recovery v6.0.1.5
-Mounts and Storage
-Format/System
-Format/cache
-Format/Panic
-Format/PDS
After performing this command does not install flash roms zip. Bootloop never happen before. I suspect wip panic XT890 damaged.
all current rom zip bootloop my problem
every rom install with no problem BAT.file bootloop.
YES! Install TWRP however same error happened install flash zip
SML-29 installed. new root again recoveyr. install rom zip always bootloop.
When I install rom with bat.file not bootloop. After performing wipe data / factory, Start bootloop. Did not happen SML-29 installed.
Where do I find information to correct my problem?
Can someone pass information?
Please help!
(Forgive my bad english)
Bootloop razr xt890 after wipe PDS and PANIC!
thiagomtl said:
I've somewhat had this problem on my Atrix. Check and see if it helps.
http://forum.xda-developers.com/showthread.php?t=1131649
http://forum.xda-developers.com/showthread.php?t=1575035
Click to expand...
Click to collapse
This information can be applied Bean Jelly?
It is compatible with Jelly Bean? Can I apply on XT890?
Hi, check this thread for a parcial solution.
http://forum.xda-developers.com/showthread.php?p=46161692#post46161692
sekelink said:
Hi, check this thread for a parcial solution.
http://forum.xda-developers.com/showthread.php?p=46161692#post46161692
Click to expand...
Click to collapse
This solution does not work properly.
Bootloop after installing pi-llama_v1.5 over SML29.
What do I trigger was factory option in fastboot.
installation:
SML29 rsd_lite
wipe cache + wipe cache dalvick
Pi-llama_v1.5
Bootloop occurred as expected
Rom start after selecting factory in fastboot.
But the problem persists if I try to install rom zip with traditional method.
Still awaiting a solution to the problems caused by CWM in my Xt890.
Thanks to all who are helping.
Hi, tray to install under sml26 Eu.
Enviado desde mi XT890 usando Tapatalk 2

[Q] Bootlop after failed wiping data [Solved]

Hi guys, i need your help..
I was tried to install a custom ROM and i use CWM v6 to install it (i'm on stock ROM | JB 4.3 | FW .205 | locked bootloader | recovery installed : CWM & TWRP), first step i format the /system and is successfull, then the next step wipe data/factory reset but i get stuck process on:
--- wiping data ---
clear /data done.
clear /cache...........
I don't know why, but i've been waiting for 20 minutes and still stuck like that than i decides to turning off the phone with tiny button at bottom of battery (not power button), i turn on the phone again and then i've got bootlop ( what.... where is my recovery ) i didn't noticed the recovery still in there because there is no LED notify when i turn on the phone, just SONY logo :crying:
Is that happen because wiping data didn't completed and causing my recovery also gone ?
So what should i do ? can i get the phone back again ? I have the stock ROM backup on my sd card and on my laptop because before i try to install a custom ROM, i've created current ROM backup with CWM.
please help me guys..
beespoison said:
Hi guys, i need your help..
I was tried to install a custom ROM and i use CWM v6 to install it (i'm on stock ROM | JB 4.3 | FW .205 | locked bootloader | recovery installed : CWM & TWRP), first step i format the /system and is successfull, then the next step wipe data/factory reset but i get stuck process on:
--- wiping data ---
clear /data done.
clear /cache...........
I don't know why, but i've been waiting for 20 minutes and still stuck like that than i decides to turning off the phone with tiny button at bottom of battery (not power button), i turn on the phone again and then i've got bootlop ( what.... where is my recovery ) i didn't noticed the recovery still in there because there is no LED notify when i turn on the phone, just SONY logo :crying:
Is that happen because wiping data didn't completed and causing my recovery also gone ?
So what should i do ? would i get the phone back again ? I have the stock ROM backup on my sd card and on my laptop because before i try to install a custom ROM, i've created current ROM backup with CWM.
please help me guys..
Click to expand...
Click to collapse
You wiped /system so your recoveries are gone.
On older Recoveries using the wipe to install new rom can take ages so just leave it and eventually it will finish, latest version of Philz (in Bagyusz/Nexus ROMs) seems to fix this issue.
Use DSSMEX triple recovery and use philz not cwm as its a much nicer recovery (but the clean still takes ages as its an older version)
Use flashtool to flash stock rom and start from scratch to re-install custom rom.
Oblox said:
You wiped /system so your recoveries are gone.
On older Recoveries using the wipe to install new rom can take ages so just leave it and eventually it will finish, latest version of Philz (in Bagyusz/Nexus ROMs) seems to fix this issue.
Use DSSMEX triple recovery and use philz not cwm as its a much nicer recovery (but the clean still takes ages as its an older version)
Use flashtool to flash stock rom and start from scratch to re-install custom rom.
Click to expand...
Click to collapse
Oh god, i don't know about that, because this is the first time i've got bootlop..
Where is i can get the latest version of Philz, would you like to give the link ?
Triple recovery ? maybe 2 recovery is enough
Flashtool, okay i'll try to save my phone..
beespoison said:
Oh god, i don't know about that, because this is the first time i've got bootlop..
Where is i can get the latest version of Philz, would you like to give the link ?
Triple recovery ? maybe 2 recovery is enough
Flashtool, okay i'll try to save my phone..
Click to expand...
Click to collapse
You have bootloop because your phone is essentially empty of any OS or recoveries.
Flashtool to stock, find dssmex triple recovery and install that in stock when rooted, load into Philz, clean to install a new ROM and then just wait, it will take a while usually dont worry unless it takes over an hour.
Then flash the custom ROM of choice.
beespoison said:
Hi guys, i need your help..
I was tried to install a custom ROM and i use CWM v6 to install it (i'm on stock ROM | JB 4.3 | FW .205 | locked bootloader | recovery installed : CWM & TWRP), first step i format the /system and is successfull, then the next step wipe data/factory reset but i get stuck process on:
--- wiping data ---
clear /data done.
clear /cache...........
I don't know why, but i've been waiting for 20 minutes and still stuck like that than i decides to turning off the phone with tiny button at bottom of battery (not power button), i turn on the phone again and then i've got bootlop ( what.... where is my recovery ) i didn't noticed the recovery still in there because there is no LED notify when i turn on the phone, just SONY logo :crying:
Is that happen because wiping data didn't completed and causing my recovery also gone ?
So what should i do ? can i get the phone back again ? I have the stock ROM backup on my sd card and on my laptop because before i try to install a custom ROM, i've created current ROM backup with CWM.
please help me guys..
Click to expand...
Click to collapse
Can I know what Custom ROM are you trying to install?
Sometimes wiping could take time, and I am not sure why. If happens again in the future, just let it be.
As you are using LBL, I am unable to elaborate nor understand how recovery has gone. (WARNING: FOREIGN LANGUAGE) Recoveries for LBL are stored in the ramdisk OR the FOTAkernel. This is due to the fact that Xperia SP does not has an exclusive "recovery" partition in the rootfs. I dont know if wiping data would trash them.
You can easily recover your phone by flashing a stock ftf. You may follow this guide: http://forum.xda-developers.com/showpost.php?p=56717587&postcount=4
Oblox said:
You have bootloop because your phone is essentially empty of any OS or recoveries.
Flashtool to stock, find dssmex triple recovery and install that in stock when rooted, load into Philz, clean to install a new ROM and then just wait, it will take a while usually dont worry unless it takes over an hour.
Then flash the custom ROM of choice.
Click to expand...
Click to collapse
Thanks for your explanation sir :good:
Flashtool to stock means i need .ftf file to restore the stock rom ? is it possible to restore stock rom through nandroid backup file that i've created using cwm ?
Well, the problem is solved. My phone back again and a custom rom has been installed.
beespoison said:
Oh god, i don't know about that, because this is the first time i've got bootlop..
Where is i can get the latest version of Philz, would you like to give the link ?
Triple recovery ? maybe 2 recovery is enough
Flashtool, okay i'll try to save my phone..
Click to expand...
Click to collapse
Dont use flashtool..... Youre wasting time.
Just flash Williams kernel using fastboot and flash the custom rom you want.....
Furrydaus said:
Dont use flashtool..... Youre wasting time.
Just flash Williams kernel using fastboot and flash the custom rom you want.....
Click to expand...
Click to collapse
Thanks for your advice, but my phone has been repaired

[solved] Just another Bootloop - but this time with other complications

Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan
gebauer said:
Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan
Click to expand...
Click to collapse
I suspect that your device is boot-looping on custom ROMs because there is incompatible stuff on your /data partition. The data partition needs to be wiped and you can't really do that with ODIN. You need to find a custom recovery that allows you to flash using ODIN and that is compatible with the custom ROM you are trying to flash. You also need to wipe /data (format it) before your first boot. You will loose all your info, even the stuff that was in your internal sd but the device should boot.
BUT:
I note that you said your HOME button is not working and that is required to manually boot into recovery. Additionally, with out a booting ROM you can not issue the "adb reboot recovery" command which would do it for you. There is a trick that I have learned but I only know how to do it with "heimdall" in the Ubuntu Terminal.
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
The partitions for the kernel and recovery on this device are typically kernel and kernel2 respectively.
kernel -> kernel
recovery -> kernel2
So:
recovery -> kernel ( Will boot recovery on a normal boot ).
I hope I have explained this well enough. You are going to have to do some learning if you want to get this working. Good luck.
P.S. If you are thinking of asking follow questions, don't, Google it instead.
Heimdall: http://glassechidna.com.au/heimdall/
Meticulus said:
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
Click to expand...
Click to collapse
Dear Meticulus,
thanks a lot for your help. I was away for the week-end; thus the late reply.
With your help it took me only an hour to get my smartphone working again. The main tipps, which helped me was the Heimdal tool, which I wasn't aware off and the possibility to flash the recovery directly into the kernel...
It worked like a treat. The smartphone booted into TWRP directly, which finally gave my access to wipe the data partition.
It took a couple of trials before I was able to flash an android image back to the kernel/system but this also worked nicely.
So thanks again and this brick is solved :good:
Jan

Categories

Resources