Related
I just rooted my Nexus 1 Froyo per instructions on theUnlockr.com. I installed ADB first, Then proceded to root. I then flashed a recovery rom: recovery-RA-nexus-v1.7.0.1-cyan.img. This was successful. I then booted phone into recovery mode. Selected recovery and the first couple times I received a black screen with an exclamation point in the middle of a triangle next to green android. I flashed recovery rom once again and this time it allowed me to enter. I made my backup image and even booted into recovery mode again�wiped phone clean and restored image. I thought I was golden! Later I tried to boot into recovery mode again and I received same problem as mentioned above. I tried again no luck. I even flashed recovery rom again and It still dose not work. Why could this be happening? I even went through the steps to root phone again (that went well). But still no recovery mode. I even tried another recovery rom: recovery-RA-nexus-v1.7.0.1.img. It did the same thing. Worked one time and then nothing! I need to fix this before I load custom Roms.
Sent from my Nexus One using XDA App
follow this guide
http://forum.xda-developers.com/showthread.php?t=636795
Amritttt said:
follow this guide
http://forum.xda-developers.com/showthread.php?t=636795
Click to expand...
Click to collapse
I was able to flash recovery via your instructions but phone STILL will not boot into recovery mode. I hold down the volume key and power.....all I get is triangle with droid net to it. Im going to try and Un-root my phone and start from scratch! Thanks for the help!
you are getting the triangle with the droid because the recovery did not flash correctly, try usung rom manager if for nothing else, just to install Amon/clockwork
Poseidon20 said:
I was able to flash recovery via your instructions but phone STILL will not boot into recovery mode. I hold down the volume key and power.....all I get is triangle with droid net to it. Im going to try and Un-root my phone and start from scratch! Thanks for the help!
Click to expand...
Click to collapse
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p
you are getting the triangle with the droid because the recovery did not flash correctly, try usung rom manager if for nothing else, just to install Amon/clockwork
Cool thanks for the advice! I did try Rom Manager and used Amon/Clockwork recovery. After flashing the Recovery Image I booted into recovery from Rom Manger. No problem! BUT.....when I rebooted phone from recovery menu I again went in to Rom Manager and tried to Boot back in to recovery and I got the triangle with the Droid next to it. I pulled battery and started phone again. I flashed Amon/Clockwork recovery again from Rom Mang. and again I was able to successfully boot in to recovery. This pattern goes on and on. It seams that every-time I want to boot into recovery I need to flash Amon/clockwork image. Somewhere phone is not retaining the information. Everything looks to work just fine as long as I Flash before I go into recovery. I'm sure this is not the way it should work. Any ideas?
khaytsus said:
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p
Click to expand...
Click to collapse
Khaytsus,
When was I told to remove the two scripts? Where did this come from? Please let me know what they are for and why removing them would help? Also, if I do need to remove these would it be done by using Root File Manager, finding file and selecting delete? Sorry if I sound new to this.....it's because I am! LOL. Thanks for any help you can provide!
Try this.
http://forum.xda-developers.com/showpost.php?p=7378018&postcount=47
Poseidon20 said:
Khaytsus,
When was I told to remove the two scripts? Where did this come from? Please let me know what they are for and why removing them would help? Also, if I do need to remove these would it be done by using Root File Manager, finding file and selecting delete? Sorry if I sound new to this.....it's because I am! LOL. Thanks for any help you can provide!
Click to expand...
Click to collapse
It's documented in random places, of course the post below also has the same info. I don't know precisely what the two files do, but they apparently try to restore the recovery.
Trust me, it will fix the problem. Remove them, re-flash recovery.
khaytsus said:
It's documented in random places, of course the post below also has the same info. I don't know precisely what the two files do, but they apparently try to restore the recovery.
Trust me, it will fix the problem. Remove them, re-flash recovery.
Click to expand...
Click to collapse
Khaytsus,
You saved my Droid! You were right! deleting those 2 files worked. I'm well into flashing Custom ROMs. Your the only one who got it right! Good job! Thanks Again!
khaytsus said:
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p
Click to expand...
Click to collapse
So, I'm not the OP, but I am having trouble deleting the files despite the fact that they are both say "YES" in read and write in properties. I tried to reflash from ROM Manager and I keep getting an error there. Not sure what to do.
BTW, I'm using a Galaxy Nexus. Would love some help as this is all uncharted terrain for me.
sadako12 said:
BTW, I'm using a Galaxy Nexus. Would love some help as this is all uncharted terrain for me.
Click to expand...
Click to collapse
You are in Nexus One Q&A Forum. Did you tryed with Galaxy Nexus Recoveries files and guides ?
ldFxl said:
You are in Nexus One Q&A Forum. Did you tryed with Galaxy Nexus Recoveries files and guides ?
Click to expand...
Click to collapse
I tried pretty much everything other than wiping the whole thing again. It's quite unfortunate.
sadako12 said:
I tried pretty much everything other than wiping the whole thing again. It's quite unfortunate.
Click to expand...
Click to collapse
If I understand, your problem is that you can't actually flash a custom recovery from ROM Manager ?
Which do you use ?
Are you trying to flash a recovery in recovery mode ?
Please link here files you tried to flash.
ldFxl said:
If I understand, your problem is that you can't actually flash a custom recovery from ROM Manager ?
Which do you use ?
Are you trying to flash a recovery in recovery mode ?
Please link here files you tried to flash.
Click to expand...
Click to collapse
I can't flash from ROM Manager. Initially, I didn't want to purchase the download capability. So, first, I used the program tools and flashed from there. I got Clockwork Mod to work, but then when I restarted it and went into "recovery," I got nothing.
Now, I can't flash at all.
The galaxy nexus should have fastboot capabilities, this is the best and safest way to flash your recovery partition
Be sure to use the proper recovery image for your device
If you need help finding it or setting up fastboot let me know
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
The galaxy nexus should have fastboot capabilities, this is the best and safest way to flash your recovery partition
Be sure to use the proper recovery image for your device
If you need help finding it or setting up fastboot let me know
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have only ever found a guide for a temporary flash. I would follow the instructions and then CWM wouldn't stick. =\
So here is the typical steps to follow
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
And that's it, were you using fastboot to just boot it? Were you doing another method? The more details you give the faster and more accurate your help will be
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So here is the typical steps to follow
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
And that's it, were you using fastboot to just boot it? Were you doing another method? The more details you give the faster and more accurate your help will be
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I used instructions from http://androidforums.com/internatio...root-samsung-galaxy-nexus.html#enter-recovery.
The ROM wouldn't "stick" and then the USB wasn't even recognized by the end of everything.
Start by booting into your bootloader and writing down everything word for word on that screen here. Next boot to recovery and write down what you see there. Even better upload pics of each. Again the more detailed you can be the more help you can get
Sent from my Nexus 7 using XDA Premium 4 mobile app
Can any one please make a fully working recovery for our device? Its really painful with the current CWM. Even adb is not recognizing it..
Sent from my MB886 using xda app-developers app
flash a different rom or flash stock and start over
Aingaran said:
Can any one please make a fully working recovery for our device? Its really painful with the current CWM. Even adb is not recognizing it..
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
noobsaibot34 said:
flash a different rom or flash stock and start over
Click to expand...
Click to collapse
i tried it many times, no use.... im pretty sure, that this cwm (6.0.2.8 and 6.0.3.2) are buggy
CWM
Factory reset wipe
Mount and format system
Format sdcard
Mount system again
Wipe dalvik cache
Flash ROM
Flash gapps
The problem isn't cwm(flash it again and see)
I only had a problem upgrading to 6.0.3.2
The only differences I've seen are the cwm startup and background and it takes about 1 or 2 secs longer to format system but it works flawlessly nonetheless...
Aingaran said:
i tried it many times, no use.... im pretty sure, that this cwm (6.0.2.8 and 6.0.3.2) are buggy
Click to expand...
Click to collapse
noobsaibot34 said:
Factory reset wipe
Mount and format system
Format sdcard
Mount system again
Wipe dalvik cache
Flash ROM
Flash gapps
The problem isn't cwm(flash it again and see)
I only had a problem upgrading to 6.0.3.2
The only differences I've seen are the cwm startup and background and it takes about 1 or 2 secs longer to format system but it works flawlessly nonetheless...
Click to expand...
Click to collapse
no success...
Try the sticky bit fix from general that worked for me when I had problems upgrading then use myth tools and flash stock jb then go from there...as long as the phone works you don't need a new one! And make sure you have snapdragon fast boot files...
noobsaibot34 said:
Try the sticky bit fix from general that worked for me when I had problems upgrading then use myth tools and flash stock jb then go from there...as long as the phone works you don't need a new one! And make sure you have snapdragon fast boot files...
Click to expand...
Click to collapse
i did that too bro... adb doesnt recognise my device till it boots up, i even try to logcat, but failed.. it showed me waiting for device
Your phone is corrupted it needs to be reflashed stock boot the phone in fast boot stop trying to use adb
Aingaran said:
i did that too bro... adb doesnt recognise my device till it boots up, i even try to logcat, but failed.. it showed me waiting for device
Click to expand...
Click to collapse
noobsaibot34 said:
Your phone is corrupted it needs to be reflashed stock boot the phone in fast boot stop trying to use adb
Click to expand...
Click to collapse
i have flashed stock with all possible ways numerous number of times.. with fastboot, rsd lite, myth tools etc.. i have also did a full wipe (system, radio, sd card, cache everything) and tried installing from scrap, that too dint help me...
Just trying yo give you hope man! Get a new phone if you can then...just seems that since it worked until you did something that it could be undone I'm surprised that you didn't backup...also exactly what caused this so that no one ever does that?
Aingaran said:
i have flashed stock with all possible ways numerous number of times.. with fastboot, rsd lite, myth tools etc.. i have also did a full wipe (system, radio, sd card, cache everything) and tried installing from scrap, that too dint help me...
Click to expand...
Click to collapse
noobsaibot34 said:
Just trying yo give you hope man! Get a new phone if you can then...just seems that since it worked until you did something that it could be undone I'm surprised that you didn't backup...also exactly what caused this so that no one ever does that?
Click to expand...
Click to collapse
actually, i suspect my computer.. there are no proper drivers for windows for these stuffs....this could be the reason... i have even tried to lock the bootloader and unlock it again
Aingaran said:
actually, i suspect my computer.. there are no proper drivers for windows for these stuffs....this could be the reason... i have even tried to lock the bootloader and unlock it again
Click to expand...
Click to collapse
Did you try loading the Motorola USB drivers? Not sure if that would help.
I immediately rooted, unlocked the bootloader, and flashed CWM 6.0.2.8 as soon as I got my new AHD and haven't had any problems with CWM in terms of flashing various roms, backing up roms, and restoring roms.
BTW, I have looked around and I could not find a method to re-lock the bootloader. How did you try to re-lock?
You can't re lock it.
Sent from my PACMAN MATRIX HD MAXX
He is actually right...there is no adb support in CWM or TWRP recovery...adb will work in fastboot, but i dont think he is talking about that...
ai6908 said:
He is actually right...there is no adb support in CWM or TWRP recovery...adb will work in fastboot, but i dont think he is talking about that...
Click to expand...
Click to collapse
I've never been able to adb with this phone in recovery either. Tried everything.
Sent from my mb886 using Tapatalk 4 Beta
Yup me too...we are missing something...I know most of our recoveries were built of xt925's...maybe that is the issue...who knows...
one thing to try is to make sure that your devices id is in the 99android rules file in rules.d if you are using linux.
Hi everyone,
Basically went out and bought a new Xperia Z wanting to put a cyanogenmod on it (First try).
Managed to root it (I saw SuperSU in apps), take a backup with TA 9.6, and unlock bootloader.
I then used these commands to boot the image
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
But I then realized I had forgotten to put the rom .zip folder onto the phone.
So I tried wiping cache partition and wipe data/factory reset, thinking that might fix something.
When I plug the phone into a Win 7 computer it isn't recognized in CWM mode (No driver available)
In fastboot it installs a driver, but I can't see the phone in computer (as in I am unable to put files onto the phone).
Also, I am sure I didn't re-enable usb debugging after I unlocked the bootloader (did i need to do that?)
Tried reinstalling drivers but it doesn't seem to be working.
Doesn't matter how I trun on the phone, it just is stuck at free xperia load screen. I can still access the recovery screen.
What the hell have I done!!
Lol.... Just pull out your memory card.... Nd pit the rom.zip in it....
Flash via recovery.... Nd puff u r done
Sent from my C6603 using xda premium
rohit25 said:
Lol.... Just pull out your memory card.... Nd pit the rom.zip in it....
Flash via recovery.... Nd puff u r done
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Hi rohit25 thanks for the quick reply!
Unfortunately, my model didn't come with a external memory card, it must all be on internal...
Flash a stock ftf.
...Sent from Zed
XperienceD said:
Flash a stock ftf.
...Sent from Zed
Click to expand...
Click to collapse
Thanks so much, I had no idea what that meant until now.
But found some instructions and viola!
Hello knowledgeable people!
I did a very stupid thing!... I took an official Samsung ROM package .tar.md5, remove the .md5 extension, extracted it, replaced boot.img with a custom kernel boot.img and re-compressed into a .tar package.
Then I took this .tar package and flashed it on the phone with Odin on my PC.
That didn't work, as expected.
The process blocked at one point.
I thought I will then just have to flash the Samsung official ROM to get everything back.
Well... not! I can flash the Samsung official ROM with Odin on my PC, but when the phone starts, it get stucked on bootloop on the glowing samsung logo.
I tried many things, including:
* wipe cache
* wipe data
but nothing worked...
At this point, I think I need to repartition/format everything and start from scratch but I don't know how to do this...
I tried to flash the Partition Identification Table kindly uploaded by @lyriquidperfection, but it didn't work (see here: http://forum.xda-developers.com/showthread.php?t=1950591) and it gets stuck in Odin as @narcarsiss mentions here: http://forum.xda-developers.com/showpost.php?p=33145970&postcount=2
Anyone has an idea?
> How to re-partition/re-format properly?
> Any other method to solve the bootloop?
Thanks for your help!
Why not to flash stock Sammy rom through Odin? This time - not modified?
Flash stock Sammy latest ROM .
Wipe everything in recovery and it should work.
I always have to wipe **** when installing official Sammy ROM.
Else it will stay at Samsung screen with flashing letters
Sent from my GT-I9305 using xda app-developers app
Hbohd said:
Why not to flash stock Sammy rom through Odin? This time - not modified?
Click to expand...
Click to collapse
This is what I tried... but it still get stuck at glowing samsung logo...
toeterbaas said:
Flash stock Sammy latest ROM .
Wipe everything in recovery and it should work.
I always have to wipe **** when installing official Sammy ROM.
Else it will stay at Samsung screen with flashing letters
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the answer.
What do you mean "wipe ****"?
Could you detail the steps?
1. Flash official sammy ROM through odin
2... enter recovery? (please confirm)
3... wipe what?
Thanks!
Have you tried flashing another kernel?Boeffla Etc then use KIES or Odin to flash back to stock
Sent from my GT-I9305 using xda app-developers app
Yes enter recovery after flashing with Odin.
When u power on hold volume up home key and power all at the same time release them when u see Samsung gt i9305 then wipe cach and wipe the other one. There are 2 wipe options.
Your phone should boot now it takes some time the first time around a minute.
Let me know if it worked
- flash stock Samsung ROM for your country with Odin
- go to recovery wipe the 2 options When u power on hold volume up home key and power all at the same time release them when u see Samsung gt i9305
-phone should boot takes a minute before he goes trough the flashing Samsung screen.
Sent from my GT-I9305 using xda app-developers app
---------- Post added at 09:51 AM ---------- Previous post was at 09:47 AM ----------
All you have to do is follow my steps.
It should work now
Sent from my GT-I9305 using xda app-developers app
Looki75 said:
Hello knowledgeable people!
I did a very stupid thing!... I took an official Samsung ROM package .tar.md5, remove the .md5 extension, extracted it, replaced boot.img with a custom kernel boot.img and re-compressed into a .tar package.
Then I took this .tar package and flashed it on the phone with Odin on my PC.
That didn't work, as expected.
The process blocked at one point.
I thought I will then just have to flash the Samsung official ROM to get everything back.
Well... not! I can flash the Samsung official ROM with Odin on my PC, but when the phone starts, it get stucked on bootloop on the glowing samsung logo.
I tried many things, including:
* wipe cache
* wipe data
but nothing worked...
At this point, I think I need to repartition/format everything and start from scratch but I don't know how to do this...
I tried to flash the Partition Identification Table kindly uploaded by @lyriquidperfection, but it didn't work (see here: http://forum.xda-developers.com/showthread.php?t=1950591) and it gets stuck in Odin as @narcarsiss mentions here: http://forum.xda-developers.com/showpost.php?p=33145970&postcount=2
Anyone has an idea?
> How to re-partition/re-format properly?
> Any other method to solve the bootloop?
Thanks for your help!
Click to expand...
Click to collapse
Tnx for the mention, but i heade bad news. I had to send my phone away to fix the issue.
This was a long time ago that this happened and better methods may of been discovered. Good luck:good:
narcarsiss said:
Tnx for the mention, but i heade bad news. I had to send my phone away to fix the issue.
This was a long time ago that this happened and better methods may of been discovered. Good luck:good:
Click to expand...
Click to collapse
Thanks for your answer!
I fear sending S3 to Samsung for repair is the only way, unfortunately... This is what I will do tomorrow (in 10hrs from now) unless a white knight arrives on this thread and gives me the golden solution!
You havent mentioned what rom version you tried.
I guess you used 4.3 official?
I could only guess but ther is probably more then just boot.img containing Knox code.
Knox is hindering users from downgrading bootloader and that maight be your problem now.
You did not mention wich version you try to recover to either.
So if you try with the old 4.1.2 it may be impossible.
Perhaps you need the newest official rom to get it working.
Sent from my GT-I9305 using XDA Premium 4 mobile app
tissot said:
You havent mentioned what rom version you tried.
I guess you used 4.3 official?
I could only guess but ther is probably more then just boot.img containing Knox code.
Knox is hindering users from downgrading bootloader and that maight be your problem now.
You did not mention wich version you try to recover to either.
So if you try with the old 4.1.2 it may be impossible.
Perhaps you need the newest official rom to get it working.
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your answer.
The home made package was on 4.3 base.
Then I tried to reflash official 4.3.
I will give a try with 4.1.2...
Well... didn't work either... since I already had knox bootloader...
It shows "unsupported version".
Oh well...
tissot said:
You havent mentioned what rom version you tried.
I guess you used 4.3 official?
I could only guess but ther is probably more then just boot.img containing Knox code.
Knox is hindering users from downgrading bootloader and that maight be your problem now.
You did not mention wich version you try to recover to either.
So if you try with the old 4.1.2 it may be impossible.
Perhaps you need the newest official rom to get it working.
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can't flash the old version. Odin will revert it back while installing.
Sent from my GT-I9305 using xda app-developers app
Looki75 said:
Thanks for your answer.
The home made package was on 4.3 base.
Then I tried to reflash official 4.3.
I will give a try with 4.1.2...
Click to expand...
Click to collapse
Okey
A bit far feched but is it possible your download is broken? Try DL again.
And either it is or not you could try installing 4.3 from different region as yours. Just to try every possability.
It shouldnt be impossible to fix this stupid phone
You dont have any nandroid backup some where.
Last option. Throw it on a brick wall to release som aggrevation and then you buy a Nexus 5. Problem solved.
Sent from my GT-I9305 using XDA Premium 4 mobile app
tissot said:
Okey
A bit far feched but is it possible your download is broken? Try DL again.
And either it is or not you could try installing 4.3 from different region as yours. Just to try every possability.
It shouldnt be impossible to fix this stupid phone
You dont have any nandroid backup some where.
Last option. Throw it on a brick wall to release som aggrevation and then you buy a Nexus 5. Problem solved.
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You made me laugh!
Seriously: DL is OK (I flashed this very official ROM many times in the past) and I do have a nandroid, but result is the same (stuck at glowing samsung logo).
The issue is way deeper.
Thanks for your help! Before trying the brick wall, I will try to make it repaired by Samsung!
Looki75 said:
You made me laugh!
Seriously: DL is OK (I flashed this very official ROM many times in the past) and I do have a nandroid, but result is the same (stuck at glowing samsung logo).
The issue is way deeper.
Thanks for your help! Before trying the brick wall, I will try to make it repaired by Samsung!
Click to expand...
Click to collapse
I had a brick once, butthe situation was a bit different. I have knox bootloader and tried to downgrade to a 4.1.2 rom without the bootloader package. The flash went ok, but my phone was stucked on Samsung Galaxy S3 GT-I9305 screen. After that, i was quite desperate and tried to reflash stock 4.3 via odin, but it failed :S
Then i tried to flash official Germany's 4.3 again, this time with the ODIN version inside CF-Root package (http://download.chainfire.eu/232/CF-Root1/CF-Auto-Root-m3-m3zh-gti9305.zip?retrieve_file=1), put the cable in another USB port, killed every kies proccess and rebooted phone in dowwnload mode. This time the flash went ok, i rebooted the phone into recovery (got bootloop) and wipe cache and factory reset. After this the phone booted up normally. Hope you can fix your phone
shucrut said:
I had a brick once, butthe situation was a bit different. I have knox bootloader and tried to downgrade to a 4.1.2 rom without the bootloader package. The flash went ok, but my phone was stucked on Samsung Galaxy S3 GT-I9305 screen. After that, i was quite desperate and tried to reflash stock 4.3 via odin, but it failed :S
Then i tried to flash official Germany's 4.3 again, this time with the ODIN version inside CF-Root package (http://download.chainfire.eu/232/CF-Root1/CF-Auto-Root-m3-m3zh-gti9305.zip?retrieve_file=1), put the cable in another USB port, killed every kies proccess and rebooted phone in dowwnload mode. This time the flash went ok, i rebooted the phone into recovery (got bootloop) and wipe cache and factory reset. After this the phone booted up normally. Hope you can fix your phone
Click to expand...
Click to collapse
Thanks! Any idea is valuable!
How did you create the ball pack of "4.1.2 rom without the bootloader" - in other words: how did you remove the bootloader from there?
Looki75 said:
Thanks! Any idea is valuable!
How did you create the ball pack of "4.1.2 rom without the bootloader" - in other words: how did you remove the bootloader from there?
Click to expand...
Click to collapse
I'd used this tutotial (just the part of commands, added everything that the original ".md5" has, removing just the "sboot.img", i'm not 100% sure if this is the only file to be off the new package, as i said, didnt work for me ), the only difference is that i'm using cygwin instead of linux itself, it worked like a charm
Basically all u need to do is unpack a original .md5 firmware (use winrar or so) and move the files (except sboot.img) to your home directory of linux or, in my case, cygwin (originally C:\cygwin\home\user-name), start the console and type the command bellow, switching the ".imgs" to match yours, of course:
Code:
cd $HOME
tar -H ustar -c image_1 image_2 > your_odin_package.tar
After this you must have a 1Gb+ .tar file (considering you will make a stock samsung flashable), now you will add md5 checksum to that, just to avoid troubles:
Code:
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
and voilà, you have your flashable odin package. Of course you can try making one with just the system.img, boot.img and modem.img. If the phone boots up, do a factory reset. I have no idea if this will work in any occasion having knox bootloader trying to flash official 4.1.x, but you can also try with a samsung 4.3 rom.
In the last scenario, try to CF auto-root your phone, then flash an official CWM recovery via odin using this method i told u, boot into recovery and flash a custom rom, do a factory reset and wiping cache and dalvik cache. I hope one of the options work for you.
I'd recommend trying to flash a custom recovery and then a custom rom. If phone boots up and is functional, try to flash samsung official 4.3 again (if your desire is having the stock of course), not forgeting to factory reset via cwm first to avoid troubles.
Been in maybe like pratically the same situation
1st flash philz touch recovery ( install latest version)
2nd backup ur efs in external sd and copy it to a pc just in case (important if u mess up imei )
3rd Copy and rom in the external sd
4th Wipe data,cache,dilvik
5th In mount and storage Format everything except external sd ( u can backup ur internal sd card with 3rd step)
6th Flash Rom and reboot
7th If no imei then try a newer modem
http://forum.xda-developers.com/showthread.php?t=2572432
http://forum.xda-developers.com/showthread.php?t=2607279
Notice I only could get to run 4.3 to run after formating everything through philz touch recovery
Hi. I've been using Omar Avelar's ROM for very long time with no problems until today
I downloaded 28th August version to my cel, put it in recovery with CWM, wipe cache and install the zip like every single time but at the end of the instalation it failed, the I reboot it and get stuck in bootloader
Fortunately still have access to recovery, try to reinstall the zip and still failed at the end
Finally, I did wipe data and reboot it and still stuck in bootloader
I dont know what else to do
Thanks
Paulomp91 said:
Hi. I've been using Omar Avelar's ROM for very long time with no problems until today
I downloaded 28th August version to my cel, put it in recovery with CWM, wipe cache and install the zip like every single time but at the end of the instalation it failed, the I reboot it and get stuck in bootloader
Fortunately still have access to recovery, try to reinstall the zip and still failed at the end
Finally, I did wipe data and reboot it and still stuck in bootloader
I dont know what else to do
Thanks
Click to expand...
Click to collapse
Good u can get into recovery. But i have the feeling u have a serious bug. In the EMMC firmware. It is also called a superbrick in the galaxy s2 forums.
Try to flash your stock firmware back. Latest stock firmware from your region. Don't use RSD-Lite. Use mFastboot and only try to flash the boot image, system image and erase userdata and cache. Don't use rsd-lite or flash your recovery. We maybe can get it all to work if your recovery keeps working.
Hazou said:
Good u can get into recovery. But i have the feeling u have a serious bug. In the EMMC firmware. It is also called a superbrick in the galaxy s2 forums.
Try to flash your stock firmware back. Latest stock firmware from your region. Don't use RSD-Lite. Use mFastboot and only try to flash the boot image, system image and erase userdata and cache. Don't use rsd-lite or flash your recovery. We maybe can get it all to work if your recovery keeps working.
Click to expand...
Click to collapse
I forgot to say that my PC doesnt recognize my cell when i plugged it.
I'm not an expert in this programming stuff but I understand most of the steps that you told me.. Can I still flash the latest stock firmware even though my PC doesnt recognize my cel? and do you have a link of mFastboot please?
Paulomp91 said:
I forgot to say that my PC doesnt recognize my cell when i plugged it.
I'm not an expert in this programming stuff but I understand most of the steps that you told me.. Can I still flash the latest stock firmware even though my PC doesnt recognize my cel? and do you have a link of mFastboot please?
Click to expand...
Click to collapse
See my signature for it. There is a mFastboot file in there. If you are in ap fastboot mode the PC should see your device almost always. If not, you don't have the usb drivers correctly installed. U can find that also somewhere in my signature.
Hazou said:
a serious bug. In the EMMC firmware. It is also called a superbrick in the galaxy s2 forums.
Click to expand...
Click to collapse
Hi Hazou,
did u have more infos about this "emmc superbrick"?
I´m a little afraid because there are more and more people getting this brick...
what is the cause? broken memory cells due to wear?
5m00v3 said:
Hi Hazou,
did u have more infos about this "emmc superbrick"?
I´m a little afraid because there are more and more people getting this brick...
what is the cause? broken memory cells due to wear?
Click to expand...
Click to collapse
This is just what i observed. I totally don't know if it is true that we have the same problem as the superbrick, but the evidence is "almost" undeniable.
I never had a problem as the superbrick. never had a galaxy or a device with it, so i know this only through research from the internet.
Here is an explanation. It has to do with the blkdiscard command. When the device performs a partition wipe, there is a chance that a sector will get corrupt (beacuse of bad eMMC firmware). Everything before the corrupted sector still will work. Everything after it is unreachable. We can reach it by changing the partition table, but there is no research in it for the Razr I.
This bug has only been seen in just a couple emmc modules. so it affects just some devices after android 4.0.4. And our Razr I can be one of them. The bug got introduced in jellybean.
The problem can be easy avoided with a patch in kernel/ext4_utils, not solved when it already happened. But i am waiting for 4.4.2 and see if it is still present in the firmware or i will contact motorola for it.
This bug happens it both unlocked as locked bootloader. U can't avoid it. U just are unlucky when u have it. And in almost all cases it appears only when updating your rom. So if u don't do anything to your phone, then the chance is slim.
I personally have wiped/flashed (for cm10) my device many, many times. And never had it. I just hope that it is solved with 4.4.2 so the chance that u get it will get even slimmer then it now is.
Did you copy the ROM's zip file from your computer? It uses MTP instead of mass storage mode and I've found that it doesn't always copy the the whole file, but cuts off half way through. This leaves a zip file that is around 200MB and it can still be flashed through recovery. I usually download the ROM from the phone's browser, but if it is on the computer, I copy it on to my external SD using a USB card reader.
I had this problem on Windows 7 and now the same with Windows 8.1. Or there could be something wrong with my phone..
Sent from my XT890
Thx for the detailed explanation!
interesting link, hope 4.4.2 will improve it...
..
Totally fix my cell, thank you so much Hazou for all the help
Grettings from Peru
Paulomp91 said:
Totally fix my cell, thank you so much Hazou for all the help
Grettings from Peru
Click to expand...
Click to collapse
Now that everything works again, u can use rsd-lite and everything again. Luckily it had nothing to do with the eMMC bug. U got off clean
Glad it all works