Database Info

Is my phone toast?

Flashed the NexusBeam ICS rom and deleted the radio and bootloader img that came with the zip and now my phone wont boot at all, I was under the impression by deleting the bootloader.img it just wouldnt install the new bootloader which is what i wanted but it seemed to haved deleted mine in the process

Yup.. Deleting those files from the package would result in the bootloader and radio being wiped and replaced by nothing.. You will probably have to use Odin to flash a stock image. Hopefully someone can help you with that, as I've never used it.
This is precisely the reason I, and some others, were asking devs not to include those files in the rom package..and we were getting crap from other people about "complaining".
Sent from my Nexus S using Tapatalk

PhillyboyDROID said:
Flashed the NexusBeam ICS rom and deleted the radio and bootloader img that came with the zip and now my phone wont boot at all, I was under the impression by deleting the bootloader.img it just wouldnt install the new bootloader which is what i wanted but it seemed to haved deleted mine in the process
Click to expand...
Click to collapse
What phone do you have? to want to delete NexusBeam ICS bootloader? I have nexus s GT-I9020 & was gonna delete the radio, but thaught I would give the new ICS one a try first! (could always flash compatible radio later on!) & it works flawlessly! Then I added GlaDOS 2.4 kernel which changed the boot animation which I didn't like (simple, just deleted bootanimation.zip from system/media, then pulled original bootanimation.zip from NexusBeam zip, & replaced!)
Just dowload NexusBeam again & use cwm recovery or fastboot to reflash NexusBeam & if you want to change radio also, do it at the same time after copying your desired rado to your sd-card & wiping dalvik cache first, then if you change your stock kernel in NexusBeam to dev one, just use method I mentioned previously if you want to change your boot animation to whatever you want! Good luck!!

I cant boot into my bootloader or recovery at all....I can boot into ICS but if i try to but into my recovery from ROM manager my phone just turns off, and if i turn it off it wont turn back on until I run a unbrick program i found. Im stuck after that though, dont know how to flash bootloader without fastboot

PhillyboyDROID said:
I cant boot into my bootloader or recovery at all....I can boot into ICS but if i try to but into my recovery from ROM manager my phone just turns off, and if i turn it off it wont turn back on until I run a unbrick program i found. Im stuck after that though, dont know how to flash bootloader without fastboot
Click to expand...
Click to collapse
After you use unbrick program & get into recovery, use fastboot to flash new cwm recovery.img! (fastboot flash recovery cwm recovery.img!) Then when you're in cwm recovery, mount usb storage & put your newly downloaded NexusBeam.zip on your sd-card & install through cwm recovery!

CrackDaddy said:
After you use unbrick program & get into recovery, use fastboot to flash new cwm recovery.img! Then when you're in cwm recovery, mount usb storage & put your newly downloaded NexusBeam.zip on your sd-card & install through cwm recovery!
Click to expand...
Click to collapse
Fixed it, didnt realized i had to hold power and vol up while running the unbrick process...thanks for all your help guys

PhillyboyDROID said:
Fixed it, didnt realized i had to hold power and vol up while running the unbrick process...thanks for all your help guys
Click to expand...
Click to collapse
Glad to hear you fixed it. Don't delete the radio or bootloader files from the package again. Instead, you can just flash a different radio after flashing the rom. The updated bootloader is a keeper though.
Sent from my Nexus S using Tapatalk

Can i install a custom rom on my phone which is suffering Boot Loops?

My samsung GT S6102(galaxy y duos) is rooted and while modifying build.prop , my phone ended up getting into a boot loop. I have a backup of the original build.prop file but am unable to restore it. I am able to enter into recovery mode. Will i be able to install a custom ROM on my phone even though it is getting boot loops? or is there any way to fix the boot loops?

babai001 said:
My samsung GT S6102(galaxy y duos) is rooted and while modifying build.prop , my phone ended up getting into a boot loop. I have a backup of the original build.prop file but am unable to restore it. I am able to enter into recovery mode. Will i be able to install a custom ROM on my phone even though it is getting boot loops? or is there any way to fix the boot loops?
Click to expand...
Click to collapse
Yes you should be able to install a custom Rom if you have CWM installed and i think you could try to push your Build.prop Backup to your phone using ADB but i dont exactly know how to do that

@OP, if it's rooted then definitely. My HTC Explorer once stuck into boot loop too, I flashed with JaggyRom and it gave me a great experience.
For me, I had to take out the battery and reinsert and then was able to boot into recovery, and from there I flashed it with the custom ROM.

Thank you all
Thank you all who replied, i tried ADB but it was unable to recognize my phone. I am a complete newbie to android but i somehow modified an update.zip file to copy put the build.prop file back to system folder, flashed it in recovery mode and my phone started working again! I am going to be more careful next time, by the way how do i backup and restore using CWM?

babai001 said:
Thank you all who replied, i tried ADB but it was unable to recognize my phone. I am a complete newbie to android but i somehow modified an update.zip file to copy put the build.prop file back to system folder, flashed it in recovery mode and my phone started working again! I am going to be more careful next time, by the way how do i backup and restore using CWM?
Click to expand...
Click to collapse
Google is your friend.

Possiblw Solution
A possible solution is to flash back to your original Stock and try rooting again. the stock should get you out of boot loops

[Q] My phone is still not rooted/unlocked, and I do not understand why

I followed these steps
http://forum.xda-developers.com/showthread.php?t=2046439
I downloaded the SuperSU_bootable_FIX.zip file, unzipped it, and took the three folders that where in there and copied them into my SD card on my phone.
I ran ODIN3.
and PDA the following file VRALEC Bootchain to allow custom recovery [this went fine]
after restarting my system and going into ODIN mode again, I used BOOTLOADER with the following recover: ClockworkMod Touch Recovery 6.0.2.3
After it finished, I unplugged my phone, turned it off,, and took out my battery, restarted my phone into recovery mode.
Once there I clicked on Reboot system and when it asked me if I wanted to disable Disable recovery flash, i clicked YES
the system restarted. and when the phone started, it shows the Samsung logo with a "unlocked" icon at the bottom of it.
Here is where the issues there:
When I try to run SuperSU, I still get "there is no su binary installed and supersu cannot install it" -- Is it possible I did not place the files in the right place? Does it matter where on the SD card I put the files? Or is the issue something else?
I inserted my new Tmobile SIM card, and I still "Non-Verizon SIM" error -- I think this is related to the fact that my phone is not rooted yet? Or did the unlock fail as well? Is there something I need to do to allow for the Tmobile SIM card, or is it because I failed somewhere along the way, following those instructions?
I would really appreciate any help.

Why did you unzip the SuperSU_Bootloader_FIXED zip? That is not in the directions, anywhere. You simply just flash the zip in recovery.
Edit: I'm guessing you're new to rooting. While in custom recoveries (TWRP or CWM), you flash .zip files. While in Odin (for Samsung devices only), you flash .tar or .tar.md5 files.

SlimSnoopOS said:
Why did you unzip the SuperSU_Bootloader_FIXED zip? That is not in the directions, anywhere. You simply just flash the zip in recovery.
Edit: I'm guessing you're new to rooting. While in custom recoveries (TWRP or CWM), you flash .zip files. While in Odin (for Samsung devices only), you flash .tar or .tar.md5 files.
Click to expand...
Click to collapse
THANK YOU SO MUCH! That part was not clear to me at all, I did not understand it, I guess I am as stupid as they come.

Are there .tars inside .zips of the bootunlockwhatever.zip?
Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2

IT WAS THE FINAL STEP... and it did not work. (Stuck on boot loader warning screen)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.

I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you

I have almost the same problem as if the fastboot not install anything despite not display errors

great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.

do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom

Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!

ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors

angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.

ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.

[Completed] Help with reinstalling bootloader

Hi.
I am relatively experienced user who has rooted and installed custom roms on samsung galaxy and HTC desire phones before.
I have now attempted to root my alcatel onetouch pixi 4 (4034X) using instructions from this thread :- https://forum.xda-developers.com/android/general/alcatel-one-touch-pixi-4-t3376597
I got as far as flashing twrp recovery and now the phone is stuck in constant reboot. I downloaded alcatels mobile upgrade tool in hopes of reflashing the stock rom but it seems to be looking for a later rom than the one I have installed and keeps telling me I have the lastest and so wont flash.
So can I recover from this at all or have I just bricked my phone? Is there a way to FORCE the mobile upgrade tool to reflash the current rom rather than looking for an upgrade?
It seems that everything except the bootloader is intact so is there another tool I can use to restore the bootloader?
Any help would be greatly appreciated.

Looks like I managed to unbrick using a combination of SP Flash tool and an SPFT rom for the 4034X I found on the internet. will now try reflashing a different recovery tool.

O.K. so I think what is happening is an issue when unlocking the bootloader and not when flashing recovery.
This is what I did:-
1. Enabled developer mode.
2. Turned on usb debugging and unlocked bootloader oem
3. Rebooted phone, plugged in cable and accepted connection authorisation.
4. From windows typed adb reboot bootloader. Went into to fastboot.
5. Typed fastboot oem unlock, Pressed volume up on phone.
At this point I was put back in fastboot but none of the buttons worked and the phone looked like it had frozen. Was It wiping data at this point? There was no indication that it was doing anything.
I removed the battery and reinserted but when I restarted I got the same boot loop problem. Had to restore stock firmware AGAIN.
Am I doing something wrong?

Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?

nyarlathotep_uk said:
Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?
Click to expand...
Click to collapse
Hi & welcome to xda-assist,
you can try to force the installation of supersu systemless by this step, chances are good that this will make it boot properly.
boot into twrp >go to the terminal > and type:
echo SYSTEMLESS=false>>/data/.supersu
Don't know if the recovery you use has this terminal option but it's very likely.
You can do additional a Google search on "force SuperSU systemless" to get more information / background information..
Good luck
Sent from my OnePlus 2 using XDA Labs

Thanks for your reply Sam.
I only read that after I had found a copy of a CM13 Rom that worked with The 4034X. I basically flashed superSU first then did a wipe, then installed the custom rom and google apps nano before downloading the supersu apk from google play and reinstalling. Now I have a rooted phone with a custom rom and am somewhat happier. The reason I wanted to root was to remove the bloatware that was taking up 1.5 GB of my already measly 2GB internal memory and this new ROM only takes up .5 GB.
I still have some pain. For example many of the Rom Toolbox Pro functions don't work and I think its because the system image seems protected and refuses to mount rw no matter what I do. Even issuing a remount command using the device name from cat /proc/mounts tells me the block device is read only. I also seem to be unable to verify if I have busybox or install it due to the same reason.
It also took me some time to work out that the boot animations weren't stored in /data/local or /system/media but to /data/system/theme.
This used to be so much easier in the days of ice cream sandwich and lollipop. Ah well!

Update:- Managed to flash busybox 1.26 using a flashable zip via adb sideload in Caliv Recovery (Caliv can't see my adopted storage for some reason).
I'm happy now! Would still like to have a rw system so I can remove some system apps I don't use but its no biggie.