Black boot screen after rom flash - Motorola Droid RAZR

Hello
I have issu with many ROM, after i flash them i get black screen boot and nothing happend
The only rom i manger to get working are
http://forum.xda-developers.com/showthread.php?t=2222535
http://forum.xda-developers.com/showthread.php?t=2260951
http://forum.xda-developers.com/showthread.php?t=2396234
http://forum.xda-developers.com/showthread.php?t=1756659
Any idea why ? I try many different rom but there are the only one working!
I use SAFESTRAP and have tried different ROM slot
Thx for your help

Which version of Safestrap? Create slot, wipe data/cache, flash Rom, flash appropriate gapps, wipe dalvik, reboot.
I've never used LS 2.2 or ArtMod, but I had to install LS 2.9 on slot 3. AOKP on slot 2.

LuckiestNut419 said:
Which version of Safestrap? Create slot, wipe data/cache, flash Rom, flash appropriate gapps, wipe dalvik, reboot.
I've never used LS 2.2 or ArtMod, but I had to install LS 2.9 on slot 3. AOKP on slot 2.
Click to expand...
Click to collapse
I think i have used the wrong version of Safestrap : Safestrap-RAZR-D4-BIO-3.11.apk do you think it can be the problem here ?
Motorola Razr XT910 from Europe
Also i never wipe dalvik after flashing rom, i will try it
Thx for your help, any other suggestions ?

No, I believe that's the correct version. It's what I use, and have been recommended to use (as 3.5 seems to have some issues with some roms). Once you've created the proper romslot, run (under wipe menu) "factory reset". Then, install rom, install gapps (whatever apps are recommended by dev; then wipe cache/ dalvik cache, and reboot. You shouldn't have any problems. The proper gapps are imperative to not getting the death-by-forced-close experience, though it's easily correctable. Good luck.
EDIT
Also ensure that whatever the recommended slot is the slot you use; PA- slot 1, AOKP- slot 2, LS- slot 3. Any other roms should have listed, either in the original thread, or replies, the correct slot to install to.

Related

[Q] Flashing precautions

I just came from owning a vibrant (original galaxy s) and i've read multiple rom development threads but was surprised to see that there weren't any precautions listed when flashing a rom. i remember when we flashed roms on the vibrant, we had to:
- flash back to stock between roms
- wait at least 10 minutes after the roms were flashed for the dalvik cache to be rebuilt
- something else im forgetting at the moment (sorry it's almost 4 in the morning here).
do we not have to do this anymore with the sgs 2? is it ok to flash a gingerbread rom over cm7 and start using the phone right away after flashing? Thanks.
I follow my own procedure when I flash new ROMs, most are unnecessary, but I like keeping my phone clean of old stuff.
*IN CUSTOM ROM*
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik
4. Flash Stock ROM
*STOCK ROM*
5. Install ROM manager from Market
6. Flash CWM Recovery
7. Place .zip of a Custom Rom in internal SD memory
8. Reboot to Recovery
*PROCEDURE*
9. Wipe Data
10. Wipe Cache
11. Wipe Dalvik
12. For CM7.1, flash ROM TWICE, since it uses a new CWM Recovery. For a normal ROM, I install them twice too, just to be sure.

Trying to flash a custom rom. What Am I Doing Wrong?

Prior to trying to flash a custom rom onto my droid razr, I was on the verizon rom 4.1.2. I had root access and I installed BMM and got recovery working. I really liked CarbonRom from what I read and wanted to flash it and so I got the rom, the gapps 20130301 and I flashed the rom, then the gapps, and I rebooted. It gets stuck on the booting screen (the splash screen). I also tried flashing the jbx hybrid kernel (version 6 i believe) and out of curiousity tried flashing CM10.1 with the same gapps just to see.
None of it works, am I doing something wrong?? If so, what am i doing wrong??
Any help would be appreciated,
Thank you
FIXED
I got it working. If anyone is interested or has my same problem with BMM,
for some reason when you choose factory reset with BMM it doesn't clear /system. You need to go to Mounts & Format and manually format /system before the phone is actually cleared. Just clearing cache and data doens't do it.
myc132 said:
I got it working. If anyone is interested or has my same problem with BMM,
for some reason when you choose factory reset with BMM it doesn't clear /system. You need to go to Mounts & Format and manually format /system before the phone is actually cleared. Just clearing cache and data doens't do it.
Click to expand...
Click to collapse
Worked for me as well!

Is it possible to flash a ROM over the stock partition in SafeStrap 3.6x

I really want to use SafeStrap instead of BMM because with BMM, my SD card and internal storage get messed up on every reboot. However, I'm just not ok with partitioning in order to install a ROM; I want it installed over my Stock partition. Can I do that with SafeStrap? Whenever I try, it just boots to a black screen after the recovery.
Redjax said:
I really want to use SafeStrap instead of BMM because with BMM, my SD card and internal storage get messed up on every reboot. However, I'm just not ok with partitioning in order to install a ROM; I want it installed over my Stock partition. Can I do that with SafeStrap? Whenever I try, it just boots to a black screen after the recovery.
Click to expand...
Click to collapse
yeah you can. clear you cache and dalvik in the recovery, should start up find after that.
@Redjax Have you had any luck in doing this? I tried flashing to the stock partition (after making backups of everything, thank goodness!) and got the same black screen. Is there anything extra to do if you want to flash the Stock partition?
I flashed to the newest cm11 to stock slot on SS3.65. Here's what I did with no problems.
Activate Stock Slot
Wipe: Cache, Dalvik Cache, Android_secure, System, Data (Repeat; I always wipe everything twice, probably unnecessary, but i like to be sure)
Flash CM11 Nightly
Flash PA Gapps
Flash JBX Kernal
Flash WiFi Patch
Wipe Cache, Dalvik Cache again
Reboot
Everything worked fine first try. I realize what you flash will probably be different depending on which Rom you choose.
Sent from my Nexus 10 using xda app-developers app
coreywallen said:
I flashed to the newest cm11 to stock slot on SS3.65. Here's what I did with no problems.
Activate Stock Slot
Wipe: Cache, Dalvik Cache, Android_secure, System, Data (Repeat; I always wipe everything twice, probably unnecessary, but i like to be sure)
Flash CM11 Nightly
Flash PA Gapps
Flash JBX Kernal
Flash WiFi Patch
Wipe Cache, Dalvik Cache again
Reboot
Everything worked fine first try. I realize what you flash will probably be different depending on which Rom you choose.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Hmm.. I wiped everything except for the Android_secure... Wonder if that's what did it? I was just trying to flash the latest/first official CM11 nightly, along with DHackers no_set_metadata GAPPS.
After I flashed the phone wouldn't boot -- just red Moto symbol then black screen. I managed to get it into APX Fastboot mode, used DROID_RAZR_Utility to flash the stock rom back on to the phone (without data wipe). Lo and behold, the phone came back to life! RE-rooted and reinstalled Safestrap 3.65, and all the slots were still there -- no harm, no foul, but I thought for a good while I bricked the phone. Whew!
Ok, Off to research what the Android_secure partition is for...
I think, BMM is better than SS, don't have any problem with my device
I've been out of the loop for awhile. Back in the days of og droid we just used recovery. SS came in later allowing you to have dual boot.
If you don't want that option can you just use a recovery like CW and not use SS or BMM?
Sent from my XT912 using Tapatalk
On SS 3.65 i always wipe in my stock rom everything exept the SD card and the internal Storage and it works, i do it like that nearly a year without any problems.
Yes, I've not had a problem. I'm using Jelly Bean's ROM, and all I did was backup my Stock ROM, wipe it, and install through SafeStrap. I don't know why it wouldn't work for you...what ROM are you attempting it with?

Question about Flashing Gapps

My phone is Live With Walkman, Carbon rom, 4.4.2
I flashed a gapps, but it doesn't work correctly,
I want to flash another gapps on my rom.
What I have to do?
how can i flash another gapps on this gapps?
mzandi17 said:
My phone is Live With Walkman, Carbon rom, 4.4.2
I flashed a gapps, but it doesn't work correctly,
I want to flash another gapps on my rom.
What I have to do?
how can i flash another gapps on this gapps?
Click to expand...
Click to collapse
hi, you can flash these: http://goo.im/devs/BaNkS/GApps/4.4.2 choose the minimal package. (the normal just include g+ & gmail, which u can install from playstore)
but maybe you need to make a clean install (da a wipe data/factory reset) ; flash ROM + gapps, done.
but 1st just installl gapps from link abobe & see if all is fine may
bejunk said:
hi, you can flash these: http://goo.im/devs/BaNkS/GApps/4.4.2 choose the minimal package. (the normal just include g+ & gmail, which u can install from playstore)
but maybe you need to make a clean install (da a wipe data/factory reset) ; flash ROM + gapps, done.
but 1st just installl gapps from link abobe & see if all is fine may
Click to expand...
Click to collapse
Thanks,
If i want to flash the new Gapps on existing rom, and existing Gapps, do i have to wipe data/factory reset, after flashing?
mzandi17 said:
Thanks,
If i want to flash the new Gapps on existing rom, and existing Gapps, do i have to wipe data/factory reset, after flashing?
Click to expand...
Click to collapse
no , do this:
1 flash the gapps package i gave you link. (no wipes need just falsh)
-->if all worked then its fine.:highfive: (done)
-->if not worked: the go CWM, do wipe data/factory reset (deletes all user data..)NOW FLASH GAPPS. boot
bejunk said:
no , do this:
1 flash the gapps package i gave you link. (no wipes need just falsh)
-->if all worked then its fine.:highfive: (done)
-->if not worked: the go CWM, do wipe data/factory reset (deletes all user data..)NOW FLASH GAPPS. boot
Click to expand...
Click to collapse
thank you very much, it worked without wiping,
i have another question,
if i want to flash a new kernel on existing kernel and existing rom, what i have to do?
sorry about my low level questions.
mzandi17 said:
thank you very much, it worked without wiping,
i have another question,
if i want to flash a new kernel on existing kernel and existing rom, what i have to do?
sorry about my low level questions.
Click to expand...
Click to collapse
1. make sure kernel is compatible with ur current ROM (very important)
2. do a backup.
3. connect the phone via fastboot & flash the desired kernel as allways
4. boot right into CWM , wipe dalvik-cache & chache
5. boot. done
bejunk said:
1. make sure kernel is compatible with ur current ROM (very important)
2. do a backup.
3. connect the phone via fastboot & flash the desired kernel as allways
4. boot right into CWM , wipe dalvik-cache & chache
5. boot. done
Click to expand...
Click to collapse
thans alot :good:

Again about slot A/B

Hello! I am so sorry beforehand for my noob question but I still can't understand how it's exactly work. I have read a lot information about slot A/B and now I've faced with one question which I can't understand by my self. Firstly I flashed recovery by lineage os both A and B . Then I flash ROM by lineage OS when I was in recovery slot B. After it recovery changed to A by itself and ROM load normal but when I try from ADB to change slot to B and load to ROM from slot B I do get bootloop. I have to change slot B to A again for booting in ROM . Is it OK or I should have opportunity to load in ROM both from slot A and slot B?
BigBan123 said:
Hello! I am so sorry beforehand for my noob question but I still can't understand how it's exactly work. I have read a lot information about slot A/B and now I've faced with one question which I can't understand by my self. Firstly I flashed recovery by lineage os both A and B . Then I flash ROM by lineage OS when I was in recovery slot B. After it recovery changed to A by itself and ROM load normal but when I try from ADB to change slot to B and load to ROM from slot B I do get bootloop. I have to change slot B to A again for booting in ROM . Is it OK or I should have opportunity to load in ROM both from slot A and slot B?
Click to expand...
Click to collapse
First thing is to be able to boot either you have to completely wipe data first or neither will boot. So in essence you could have lineage on b and run till your tired then you could fastboot--set-active =a and have stock rom. But won't boot unless you wipe data between trying. Op8 here and it's basically the same thing
mattie_49 said:
First thing is to be able to boot either you have to completely wipe data first or neither will boot. So in essence you could have lineage on b and run till your tired then you could fastboot--set-active =a and have stock rom. But won't boot unless you wipe data between trying. Op8 here and it's basically the same thing
Click to expand...
Click to collapse
Without success unfortunately. What I have recovery: lineage-17.1-20201229-recovery-hotdog.img . What I did:
1) loaded in recovery slot A and wiped data and factory reset
2) loaded in recovery slot B and wiped data and factory reset
3) flashed ineage-17.1-20201229-nightly-hotdog-signed.zip
4) rebooted to recovery and it's showed slot A but I haven't changed it
5) made wipe data and factory reset in slot A again
6) loaded in recovery slot B and wiped data and factory reset and tried to load in system (unfortunately without any success)
What did I wrong or it works correct and it should be so?
BigBan123 said:
Without success unfortunately. What I have recovery: lineage-17.1-20201229-recovery-hotdog.img . What I did:
1) loaded in recovery slot A and wiped data and factory reset
2) loaded in recovery slot B and wiped data and factory reset
3) flashed ineage-17.1-20201229-nightly-hotdog-signed.zip
4) rebooted to recovery and it's showed slot A but I haven't changed it
5) made wipe data and factory reset in slot A again
6) loaded in recovery slot B and wiped data and factory reset and tried to load in system (unfortunately without any success)
What did I wrong or it works correct and it should be so?
Click to expand...
Click to collapse
You wipe one flash one reboot to other repeat
toolhas4degrees said:
You wipe one flash one reboot to other repeat
Click to expand...
Click to collapse
I'm not sure what you mean exactly but I tried to update my ROM on new version from standard point in the system and it's install in slot B automatic and then system load from slot B without any problem. Ths for your response!
BigBan123 said:
I'm not sure what you mean exactly but I tried to update my ROM on new version from standard point in the system and it's install in slot B automatic and then system load from slot B without any problem. Ths for your response!
Click to expand...
Click to collapse
I meant you wipe current slot data then flash rom then reboot to recovery which should take you to other slot then you wipe data again and flash rom again. Then reboot.
toolhas4degrees said:
I meant you wipe current slot data then flash rom then reboot to recovery which should take you to other slot then you wipe data again and flash rom again. Then reboot.
Click to expand...
Click to collapse
Why would you do it twice? Data is shared across both slots, it's redundant.
Lossyx said:
Why would you do it twice? Data is shared across both slots, it's redundant.
Click to expand...
Click to collapse
Benn doing it for 2 years wipe all the flash reboot to recovery and repeat works everytime

Categories

Resources