Database Info

[Q] Phone Stuck in Boot Loop Why?

Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!

ackerchez said:
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
Click to expand...
Click to collapse
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck

thejosh86 said:
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
Click to expand...
Click to collapse
Hey!
Thanks a ton for your reply! I managed to get the phone to install a new ROM (AOKP V5) and it seems to boot up. Now when I get into that rom, I see all kinds of things crashing on me. The "Settings" app crashes, the keyboard crashes..any idea?

Did you wipe system, factory reset, davlik and cache from within TWRP before flashing?
Try that otherwise if you're still running into issues post in the thread.

You flashed the 11/10 JB gapps?
Sent from my Nexus 7 using xda premium

ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?

ackerchez said:
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
Click to expand...
Click to collapse
Did u wipe everything? (davlik, cache)
Sent from my HTC One XL using xda premium

[Q] Custom Rom don't work

Unlocked and rooted ATT HTC One X and flashed pa_evita-2.54-09NOV2012-210217 ROM.
Boot up as far as an Android character with the lettering Paranoid Android 2.+ and then freezes there.
Any suggestions?? If nothing else, how do I get back to stock ROM?
Noob rldieb

rldieb said:
Unlocked and rooted ATT HTC One X and flashed pa_evita-2.54-09NOV2012-210217 ROM.
Boot up as far as an Android character with the lettering Paranoid Android 2.+ and then freezes there.
Any suggestions?? If nothing else, how do I get back to stock ROM?
Noob rldieb
Click to expand...
Click to collapse
1. What recovery are you using?
2. Did you wipe cache/dalvik-cache, factory reset?
In order to get back to a stock ROM, you will need to boot into recovery, then mount your usb storage. Put the rom on your sd card and then unmount. To be safe, wipe the cache and dalvic cache, then flash the stock rom.

What hboot are you on?
You may have flash boot.img first if you are on hboot 1.14

I think he just didn't full wipe

That's just wrong!
Sent from my Nexus 7 using Tapatalk 2

I'm having the same issue. I'm trying to flash this same rom on a device rooted on 2.20. I think my issue has something to do with flashing the boot.img. I have tried to flash using hasoon's toolkit, which doesnt seem to work, i have extracted the zip and placed the boot.img in the kernel folder, and when the command prompt tries to flash it, it says error. I have also tried flashing the kernel from the phone directly using the flash flash image gui app, and it says flash is successful, but when it prompts to boot into recovery, the command doesnt work from my phone so i have to boot into recovery manually.
can anyone give a solid link or tutorial on how to successfully flash the boot img onto my device, every link I have read uses windows cmd prompt, which when i try to replicate, it never works.. So, for now I flashed back to viper rom, since it has its own installer. It would be so nice if all these other roms were able to install like that.
thanks in advance for the help

threetwentyfizzle said:
I'm having the same issue. I'm trying to flash this same rom on a device rooted on 2.20. I think my issue has something to do with flashing the boot.img. I have tried to flash using hasoon's toolkit, which doesnt seem to work, i have extracted the zip and placed the boot.img in the kernel folder, and when the command prompt tries to flash it, it says error. I have also tried flashing the kernel from the phone directly using the flash flash image gui app, and it says flash is successful, but when it prompts to boot into recovery, the command doesnt work from my phone so i have to boot into recovery manually.
can anyone give a solid link or tutorial on how to successfully flash the boot img onto my device, every link I have read uses windows cmd prompt, which when i try to replicate, it never works.. So, for now I flashed back to viper rom, since it has its own installer. It would be so nice if all these other roms were able to install like that.
thanks in advance for the help
Click to expand...
Click to collapse
I do have a solution! Download Flash Image GUI from the market (it's $1.99) and it will do the process for you, no commands needed! The app is also available via XDA for free, do a search and download it.

[Q] Stuck on blackscreen

Hello, hope this isn't a duplicated thread, i didn't find anyone with the same problem over here.
I decided to install a custom rom on my mb865 (AT&T), i was on OTA ICS so i chose magicmod, here is what i did
1. Root
2. Installed Atrix2Bootstrap.apk
3. Reboot into recovery
4. Factory wipe
5. install from zip
then an error occurred during the flash
"some symlinks failed, code (or error) 7"
tried to reboot but im stucked on a black screen after the moto logo. if i press power+vol down i can get into fastboot but last time i went into fastboot it was different, i can't navigate in this one, it says
"AP Fastboot Flash Mode (S)
0A.72
Battery OK
Transfer Mode:
USB Connected"
guess i did something wrong
RSD Lite detects my phone as "Fastboot Edison S"
Did I just hard brick my phone?
pd: i couldn't post this in the magicmod thread because i'm a noob member

negroxor said:
Hello, hope this isn't a duplicated thread, i didn't find anyone with the same problem over here.
I decided to install a custom rom on my mb865 (AT&T), i was on OTA ICS so i chose magicmod, here is what i did
1. Root
2. Installed Atrix2Bootstrap.apk
3. Reboot into recovery
4. Factory wipe
5. install from zip
then an error occurred during the flash
"some symlinks failed, code (or error) 7"
tried to reboot but im stucked on a black screen after the moto logo. if i press power+vol down i can get into fastboot but last time i went into fastboot it was different, i can't navigate in this one, it says
"AP Fastboot Flash Mode (S)
0A.72
Battery OK
Transfer Mode:
USB Connected"
guess i did something wrong
RSD Lite detects my phone as "Fastboot Edison S"
Did I just hard brick my phone?
pd: i couldn't post this in the magicmod thread because i'm a noob member
Click to expand...
Click to collapse
You can get into fastboot, so you're not bricked. You should download the att ICS fxz (easily found by searching), then boot into fastboot and flash with RSDlite. Once you're back to stock ICS, you can try again to flash your rom.
Note - Before you flash your custom rom, factory reset, then wipe the cache, then the dalvik for good measure. Then flash away.
First boot can take a few minutes, so be patient.

thanks
41rw4lk said:
You can get into fastboot, so you're not bricked. You should download the att ICS fxz (easily found by searching), then boot into fastboot and flash with RSDlite. Once you're back to stock ICS, you can try again to flash your rom.
Note - Before you flash your custom rom, factory reset, then wipe the cache, then the dalvik for good measure. Then flash away.
First boot can take a few minutes, so be patient.
Click to expand...
Click to collapse
Thank you !!, my phone is alive again, i used this file in rsdlite -> "InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml" found it on google
i'll try again, btw, should i install cwm from bootstrap recovery as a zip? i saw that in a youtube video
i tried to flash straight from the bootstrapper menu.
Maybe ill try with scv7 or CM10

negroxor said:
Thank you !!, my phone is alive again, i used this file in rsdlite -> "InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml" found it on google
i'll try again, btw, should i install cwm from bootstrap recovery as a zip? i saw that in a youtube video
i tried to flash straight from the bootstrapper menu.
Maybe ill try with scv7 or CM10
Click to expand...
Click to collapse
CM10.1 is pretty solid, and has some of the bugs fixed that were present in CM10
To flash it, just install the Atrix2BootStrap, then bootstrap the recovery, reboot to recovery, do the wipes, then flash. Should be good to go.

negroxor said:
Thank you !!, my phone is alive again, i used this file in rsdlite -> "InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml" found it on google
i'll try again, btw, should i install cwm from bootstrap recovery as a zip? i saw that in a youtube video
i tried to flash straight from the bootstrapper menu.
Maybe ill try with scv7 or CM10
Click to expand...
Click to collapse
u dont need to install CWM again since atrix boot strapper provides it
1)Regarding CM10 on AT&T, u will hard brick u r mobile if u flash it
2)scv7 should have BMM not atrix boot strapper...i tried it with boot strapper and softbricked my mobile..so try scv7 with BMM only

vdpraneeth said:
u dont need to install CWM again since atrix boot strapper provides it
1)Regarding CM10 on AT&T, u will hard brick u r mobile if u flash it
2)scv7 should have BMM not atrix boot strapper...i tried it with boot strapper and softbricked my mobile..so try scv7 with BMM only
Click to expand...
Click to collapse
1 - CM10 on AT&T is fine. I'm on AT&T and I've ran it and I'm currently running CM10.1, also it's pretty near impossible to hard brick from flashing a custom rom around here since we have a locked bootloader. We're not flashing firmware specific files with customs. FXZs are a different story, everything matters with those and you need to pay attention.
2 - Bootstrap should be fine with scv7, however, in the description it says that BMM is already in the rom. So if you tried to use the Bootstrap without removing BMM first, then it will most likely bootloop you.

on CM 10.1
41rw4lk said:
1 - CM10 on AT&T is fine. I'm on AT&T and I've ran it and I'm currently running CM10.1, also it's pretty near impossible to hard brick from flashing a custom rom around here since we have a locked bootloader. We're not flashing firmware specific files with customs. FXZs are a different story, everything matters with those and you need to pay attention.
2 - Bootstrap should be fine with scv7, however, in the description it says that BMM is already in the rom. So if you tried to use the Bootstrap without removing BMM first, then it will most likely bootloop you.
Click to expand...
Click to collapse
Did it!, im running 10.1 and looks very good so far, camera working, thanks for the help!.
edit: forgot to install the gapps while i was in the bootstrap, can i flash gapps from CM's boot menu?

negroxor said:
Did it!, im running 10.1 and looks very good so far, camera working, thanks for the help!.
edit: forgot to install the gapps while i was in the bootstrap, can i flash gapps from CM's boot menu?
Click to expand...
Click to collapse
Yes, just boot into the built in recovery, flash gapps, wipe dalvik, reboot.

Need serious help restoring OPO

I am really needing some advise. I was having a funny pop up a couple of days ago on my OPO saying that google music has stopped. I am running the 33 update at this time rooted with twrp. So, I froze the app with titanium back up. I went to flash MAHDI rom right now and when I wiped the phone red lettering popped up saying E.error opening:/data/data/com.google.android.music:I/O error
But it said it wiped successfully. So I flashed MAHDI and gapps and when I booted I got this message unfortanutley the process android system has stopped, and under that was another message that said, system UIDs inconsistent you need to wipe your data partition or your device will be unstable
So I wiped everything again and still got the red lettering pop up. I tried restoring a previous back up and it fails. Now I am back in twrp but I am lost on what to do.
Is there a way just to flash back to stock? Is there a fix that anyone knows about? I highly appreciate any help. Thanks again!

I don't clearly understand your problem 100%, maybe its because its 3:05 AM and I have not gone to sleep yet.
1. Use TWRP -> Wipe -> Swipe
2. Flash Mahdi ROM, Gapps, Kernel (if you use one)
3. Reboot
4. You'll have a clean scratch.
You shouldn't be having any errors with a clean scratch. You probably didn't wipe correctly. You don't need to change any mount or wipe, the defaults will wipe it. But since you changed it, you need to reset it back.
Worst comes to worst if you really want to flash back to stock. Then look up on XDA about fastbooting back to stock.You can find the 33R Images https://cyngn.com/products/oneplusone/

zephiK said:
I don't clearly understand your problem 100%, maybe its because its 3:05 AM and I have not gone to sleep yet.
1. Use TWRP -> Wipe -> Swipe
2. Flash Mahdi ROM, Gapps, Kernel (if you use one)
3. Reboot
4. You'll have a clean scratch.
You shouldn't be having any errors with a clean scratch. You probably didn't wipe correctly. You don't need to change any mount or wipe, the defaults will wipe it. But since you changed it, you need to reset it back.
Worst comes to worst if you really want to flash back to stock. Then look up on XDA about fastbooting back to stock.You can find the 33R Images https://cyngn.com/products/oneplusone/
Click to expand...
Click to collapse
Thank you for your response! I tried doing the above by wiping but it would never boot up correctly. Always kept crashing on boot. I now wiped the whole phone and I am still in twrp but now everything is gone, including my nandroids, and all roms along with Mahdi. So, it looks like I will have to flash back to stock using fastboot mode.
I highly appreciate your help and I am glad to donate something. I don't mind buying lunch :good:
Are the images in a flashable zip or called a snapshot?

rayandreas said:
Thank you for your response! I tried doing the above by wiping but it would never boot up correctly. Always kept crashing on boot. I now wiped the whole phone and I am still in twrp but now everything is gone, including my nandroids, and all roms along with Mahdi. So, it looks like I will have to flash back to stock using fastboot mode.
I highly appreciate your help and I am glad to donate something. I don't mind buying lunch :good:
Are the images in a flashable zip or called a snapshot?
Click to expand...
Click to collapse
You don't need to go back to stock, alternatively, you can use adb sideload which will push the zip onto your phone and then proceed with a flash.
ADB Sideload is very easy to use, you go into recovery and plug your phone into your computer. Have adb environment set up (if you were going to fastboot, you'd need fastboot which would come with adb anyways) and then adb sideload the .zip over to your phone.
The images are in a flashable zip but thats for 25R which you will need to get yourself back up to 33R or you can fastboot flash 33R or flash a custom ROM of your choice.

zephiK said:
You don't need to go back to stock, alternatively, you can use adb sideload which will push the zip onto your phone and then proceed with a flash.
ADB Sideload is very easy to use, you go into recovery and plug your phone into your computer. Have adb environment set up (if you were going to fastboot, you'd need fastboot which would come with adb anyways) and then adb sideload the .zip over to your phone.
The images are in a flashable zip but thats for 25R which you will need to get yourself back up to 33R or you can fastboot flash 33R or flash a custom ROM of your choice.
Click to expand...
Click to collapse
Thank you very much for taking time to help me. Here is just a little something to show my appreciation. Confirmation number: 1JL24849R60212845

[Q] to root or not to root

Hello,
1st.: while starting this new thread, I looked through the automaticly generated similar threads and found non that was suiting my problem.
Last night I unlocked the bootloader of my wifes Xperia L (C2105) and got stuck into an boot loop. After this I had the need to flash an original rom (4.1.2). This results in an total wipe of the phone :crying:
Now the phone has an unlocked bootloader and an old Android Version. I want to install the pacman rom 4.4.4. I know i have to use cwm or twrp to do this, but do I need to root the device?
I'm a little bit confused. I thought installing the *.img-File from TWRP, with the folloing command, will get me the recovery option an with this option
Code:
c:\fastboot\Fastboot.exe flash boot C:\fastboot\openrecovery-twrp-2.8.4.0-taoshan.img
Can anyone help me out?
My wife is not upset, but with the boot loop from last night in my mind, I'm quit unsure what to do next.
many thanks in advanced
Felix

you need to root the device and use flashtool by androxyde(Easier and user friendly), first download the rom and put it in internal/external memory and then install thunderzap 4.12 by select bootkk.img and install it in fastboot mode in flashtool, now enter the recovery go into wipe and format options and choose clean to install a new ROM and then flash the pac rom and reboot

Root isn't necessary.
Download PAC ROM, Take boot.img inside the zip.
Flash boot.img via fastboot.
Boot into recovery, wipe data / factory reset.
Flash ROM and GApps.
That's it

NOP, you dont need to root to install a custom rom
felix leiter said:
Hello,
1st.: while starting this new thread, I looked through the automaticly generated similar threads and found non that was suiting my problem.
Last night I unlocked the bootloader of my wifes Xperia L (C2105) and got stuck into an boot loop. After this I had the need to flash an original rom (4.1.2). This results in an total wipe of the phone :crying:
Now the phone has an unlocked bootloader and an old Android Version. I want to install the pacman rom 4.4.4. I know i have to use cwm or twrp to do this, but do I need to root the device?
I'm a little bit confused. I thought installing the *.img-File from TWRP, with the folloing command, will get me the recovery option an with this option
Code:
c:\fastboot\Fastboot.exe flash boot C:\fastboot\openrecovery-twrp-2.8.4.0-taoshan.img
Can anyone help me out?
My wife is not upset, but with the boot loop from last night in my mind, I'm quit unsure what to do next.
many thanks in advanced
Felix
Click to expand...
Click to collapse
you can download the rom, extract it and keep, boot.img file, in fastboot folder, and also keep the downloaded rom zip file in sd card for later use.
than you can use use fastboot commands to flash those boot.img which will install the recovery into your phone, than .
use reboot command in fastboot, it will reboot your phone, take out your cable, using volume up key go to recovery,
there clear all the cache and delvik cache file, then, install your custom rom by selecting from your sd card, it will take a bit of time for first time, so don't worry,
than you are done,