Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] Razr I stuck in bootloader

OP Paulomp91

29th August 2014, 01:17 AM   |  #1  
OP Junior Member
Thanks Meter: 1
 
4 posts
Join Date:Joined: Aug 2014
More
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
29th August 2014, 11:26 AM   |  #2  
Hazou's Avatar
Senior Member
Thanks Meter: 1,017
 
741 posts
Join Date:Joined: Feb 2012
Donate to Me
More
Quote:
Originally Posted by Paulomp91

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

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.
The Following User Says Thank You to Hazou For This Useful Post: [ View ]
29th August 2014, 02:51 PM   |  #3  
OP Junior Member
Thanks Meter: 1
 
4 posts
Join Date:Joined: Aug 2014
More
Quote:
Originally Posted by Hazou

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.

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?
29th August 2014, 03:40 PM   |  #4  
Hazou's Avatar
Senior Member
Thanks Meter: 1,017
 
741 posts
Join Date:Joined: Feb 2012
Donate to Me
More
Quote:
Originally Posted by Paulomp91

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?

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.
29th August 2014, 04:10 PM   |  #5  
Senior Member
Flag Hamburg, DE
Thanks Meter: 46
 
129 posts
Join Date:Joined: Nov 2013
More
Quote:
Originally Posted by Hazou

a serious bug. In the EMMC firmware. It is also called a superbrick in the galaxy s2 forums.

Hi Hazou,

did u have more infos about this "emmc superbrick"?
Im a little afraid because there are more and more people getting this brick...
what is the cause? broken memory cells due to wear?
29th August 2014, 04:48 PM   |  #6  
Hazou's Avatar
Senior Member
Thanks Meter: 1,017
 
741 posts
Join Date:Joined: Feb 2012
Donate to Me
More
Quote:
Originally Posted by 5m00v3

Hi Hazou,

did u have more infos about this "emmc superbrick"?
Im a little afraid because there are more and more people getting this brick...
what is the cause? broken memory cells due to wear?

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.
The Following User Says Thank You to Hazou For This Useful Post: [ View ]
29th August 2014, 08:01 PM   |  #7  
waj3k's Avatar
Senior Member
Flag Midlands, UK
Thanks Meter: 55
 
212 posts
Join Date:Joined: Jan 2007
Donate to Me
More
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
Last edited by waj3k; 29th August 2014 at 09:55 PM. Reason: Spelling
29th August 2014, 09:14 PM   |  #8  
Senior Member
Flag Hamburg, DE
Thanks Meter: 46
 
129 posts
Join Date:Joined: Nov 2013
More
Thx for the detailed explanation!
interesting link, hope 4.4.2 will improve it...
31st August 2014, 12:42 AM   |  #9  
OP Junior Member
Thanks Meter: 1
 
4 posts
Join Date:Joined: Aug 2014
More
..
Last edited by Paulomp91; 31st August 2014 at 03:13 AM. Reason: nevermind
3rd September 2014, 06:48 AM   |  #10  
OP Junior Member
Thanks Meter: 1
 
4 posts
Join Date:Joined: Aug 2014
More
Totally fix my cell, thank you so much Hazou for all the help
Grettings from Peru

The Following User Says Thank You to Paulomp91 For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes