Database Develop

So Frustrated, cant install any thing on phone

When i woke up in morning the IMEI was missing, i was able to restore by going to stock but now i cant upgrade anything, i got boot loops when i try install ICS GB or anything, i have by mistake installed an arabic base band, and i am from israel.
currently this is my specs:
Firmware:2.2.1
BaseBand: I9000JXJPF
Kernal:2.6.32.9 [email protected] #1
Build:FROYO,JPJPM
Please help, i have a flight tomarrow and i cant be with out phone!

https://www.dropbox.com/s/apqpr3ulmihe7mq/ezbase recovery kit gb.zip
Follow the instructions in the zip file.

Installation was complete but now the phone dont turn on at all!

Remove the battery wait 5 minutes and try to turn it on.

I have managed to get to Download mode again, i have re flashed and now its stuck in boot loop.

Hey, in the end the problem was the buttery was dead, the phone managed to turn on, now can i flash any ICS that i want? what do i need to do to be sure i wont get bricked again?

nickless09 said:
Hey, in the end the problem was the buttery was dead, the phone managed to turn on, now can i flash any ICS that i want? what do i need to do to be sure i wont get bricked again?
Click to expand...
Click to collapse
First of all,u can't be sure not to semi-brick yr phone again and yes u can flash any ICS roms..
But always read the OP(first post's) and last 3 pages in the thread of the ROM u want to flash,first to ensure how to flash without problems and last to read if any bugs is current in the ROM u are about to flash..
ALWAYS have nandroid backup(cwm) and backup your EFS folder(imei)using eg.EFS-pro or nitrality app(save this to your pc or dropbox) from market.
PS..always flash with a full battery

My phone is up now.
i understand i need to install CWM recovery, but last time i got bricked, can you please tell me what to do if i want say this rom:
http://forum.xda-developers.com/showthread.php?t=1592131

nickless09 said:
My phone is up now.
i understand i need to install CWM recovery, but last time i got bricked, can you please tell me what to do if i want say this rom:
http://forum.xda-developers.com/showthread.php?t=1592131
Click to expand...
Click to collapse
Read the first post in the thread. It's all there for you. If your phone is rooted and you have CWM (ClockWorkMod Recovery) installed, then do this (which is from the first post in that thread):
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition + format /system)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
WIPE again or Calendar Sync will not work.

Trying to install 4.4 Rom, falling at every hurdle.

Hi There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers

Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?

If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk

eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.

Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app

shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone

SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk

Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!

Need help bricked phone :(

i recently flashed the eXistenZ Ultra 2, and im sure i did everything fine, after flashing the rom in recovery and flashing suprsu and wifi fix, i powered off the phone, and powered on but sony logo has apeared until now , and welcoming`s sounding 999..times. i cant turn it off, or i should say i cant do anything.
please help,

After flashing ROM and the fixes you should flash the 12.1.A.0.266 Firmware with FlashTool!
If problem still persists:
http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Take a look at this site A recovery would be quite useful, but I think the kernel of eXistenZ ROM has one. If not, you'll find one in the development section. Otherwise, use the ADB as solution.
Good luck

Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?

eefathi said:
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
Click to expand...
Click to collapse
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!

Schokonuss said:
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Click to expand...
Click to collapse
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.

eefathi said:
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
Click to expand...
Click to collapse
You're welcome
1. Do you have SuperSU installed? On AOKP ROM I'm running it asked for superuser permission for ROM Control (the control center implemented in the settings of the ROM). Maybe it'll ask you if SuperSU is installed. Otherwise, because it is after the first boot it needs to rebuild cache and so on.. If problem persists after reboot, just use an other clock speed controler (No-frills CPU, SetCPU..)
2. If you did that at the same time, maybe Go Backup didn't really backup your data. Try again, if it doesn't work and if you have a nandroid backup (backup from recovery) you can go into recovery, then to advanced restore and restore data. Otherwise your data is unfortunately gone I think :/
PS: I prefer Titanium Backup

[Q] Razr i - no possibility to flash custom rom or stock - bricked?

Hallo together,
I seem to have done something wrong while trying to flash the rom "RazRi_JB_X-2014-Jul-16".
Here is what i did:
- Unlocked to bootloader using official Motorola homepage
- Flashed CWM (non-touch) recovery using "Recovery Flasher by LeBobo v1.7", USB-Debugging was on
- Rebooted into bootloader and flashed "RAZRiRoot2" to prevent Stock-ROM from overwriting the recovery
- Tried to install the Custom ROM using CWM, but it fails to wipe cache (stuck on line "Formatting /cache")
Because it didn't work, i tried to reset everything as it was before to be able to try again - flashed stock-recovery using the Recovery Flasher by LeBobo, booted into bootloader and selected "Factory". The cell is now just showing the "Warning bootloader unlocked" warning and nothing else happens.
When i try to select the recovery in the bootloader menu, an image of a Android laying on its back with an opened hatch and a red warning symbol showing a "!" appears and nothing else happens.
I seem to have bricked my device, because i cant't really do anything now - is there any solution?
I read through different topics but could not find a real solution to this particular problem...
Thank you so much in advance for your help!

It's not bricked
At the moment u enter stock recovery with that android and red warning sy,bol, u need to press bot volume up + downp. Than it will enter stock recovery mode.
Those are the following things u can do to get custom rom,
1. Flash another recovery, cwm touch, cwm non-touch, twrp. They all work a little different.
2. Flash the custom rom and wipe everything, The wip can take some time. sometimes it will be seconds, sometimes it will take a couple of minutes. Every recovery behaves different, and every flash/wipe too.
3. enjoy
If u really want to go back to stock, flash your stock JB firmware by RSD-Lite.

Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?

StarGeneral said:
Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?
Click to expand...
Click to collapse
5 minutes is a bit too much. But that's the problem with this device. Every device behaves different and we haven't found out a solution too it.
At the moment i can't do much for you. I can only say try to wipe the partitions mannualy. Wipe system, data and cache. and mount system. And then try to install it. Maybe if that doesnt do the trick try again another recovery.
This from KTR-ROM
Code:
- Enter in TWRP or CWM
- Wipes required: data, system, cache y dalvik
*In CWM mount system must format before (Mount and storage -> Mount system)

Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!

StarGeneral said:
Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!
Click to expand...
Click to collapse
nice, glad that it worked

Flashing other roms than Andro X doesn't work

I just updated my bootloader and whenever i try to flash a rom, the booting process takes forever until i wipe my phone myself. But when i flash Andro X rom than it takes max. 3min to boot and then it works.
But i want another rom, how do i fix this?

Do you mean that when u flash lollipop based rom it gets bootloop? if yes then first flash stock lollipop firmware and then try flashing other rom. I mostly wipe my internal storage when going from Kitkat to lollipop it works for me.

Well Firstly Explain your problem clearly (I didnt quite understand it)
OK so here's my solution from what I understood..
1. Restore your stock rom Backup from recovery. Boot it once.
2. Now clean flash (Wipe System, Data , Cache, Dalvik cache) a lollipop based Rom (preferably try to clean flash cm 12.1 build)
3. Dont flash Gapps. First see if your phone boots up properly.
4. Configure data and reboot to recovery and flash Gapps.
If you dont have a Stock backup, Then download Stock Firmware images from gregor's thread and install via fastboot. Then follow from step2.
Hope this helps you.

Haroun16 said:
I just updated my bootloader and whenever i try to flash a rom, the booting process takes forever until i wipe my phone myself. But when i flash Andro X rom than it takes max. 3min to boot and then it works.
But i want another rom, how do i fix this?
Click to expand...
Click to collapse
Use easy installer first and get stock lollipop then u can simply root and install recovery then try roms?

sagar846 said:
Well Firstly Explain your problem clearly (I didnt quite understand it)
OK so here's my solution from what I understood..
1. Restore your stock rom Backup from recovery. Boot it once.
2. Now clean flash (Wipe System, Data , Cache, Dalvik cache) a lollipop based Rom (preferably try to clean flash cm 12.1 build)
3. Dont flash Gapps. First see if your phone boots up properly.
4. Configure data and reboot to recovery and flash Gapps.
If you dont have a Stock backup, Then download Stock Firmware images from gregor's thread and install via fastboot. Then follow from step2.
Hope this helps you.
Click to expand...
Click to collapse
My problem is that when i try to flash roms like CM12, Blisspop it doesn't stop booting, it was taking more than an hour so i shutdown my phone and when i flashed Andro X the booting took around 3mins.
So can anyone explain in easy steps how to fix this?

OK now I understand what your problem is. Give me your full specs (like which Model and and stuff). But if you follow what I said above it might fix your problem.

sagar846 said:
OK now I understand what your problem is. Give me your full specs (like which Model and and stuff). But if you follow what I said above it might fix your problem.
Click to expand...
Click to collapse
I got the XT1068

Haroun16 said:
I got the XT1068
Click to expand...
Click to collapse
are you fully wiping cache and userdata (factory reset) because this is most common problem moving between Roms that causes bootloops and why I include factory reset in my easy installer.
you can only dirty flash when going up (upgrading) the same rom - changing roms or downgrading nearly always causes bootloop / hang.