Database Users

Lost Boot/Recovery Img

Strange happenings going on with my Nexus S.
It has been rooted for a while and have been running Genexus S 2.0 ROM which was fine to start with but I have recently been getting lag issues with the screen, issues with character selection on the keyboard etc.
However, I have had a few crashes when the phone has been charging and the phone is being not just hot, I'm talking boiling to the touch!
I have rebooted into recovery but....recovery img and boot img have disappeared. They have been present in recent weeks but for some reason they have disappeared.
I have reinstalled clockworkrecovery via ROM Manager a couple of times but there is still no change. TBH I'm sick of the issues I've had with the phone since rooted and it's not for me so plan on going back to stock whenever I can, however, I need recovery!
Can anyone point me in the right direction to sort this out and if possible not by plugging my phone into a PC. I am away with work and don't have my own computer for a while.
Thanks

you can always flash the boot recovery back into the phone, just follow any of the how to root guides

meso100 said:
Strange happenings going on with my Nexus S.
It has been rooted for a while and have been running Genexus S 2.0 ROM which was fine to start with but I have recently been getting lag issues with the screen, issues with character selection on the keyboard etc.
However, I have had a few crashes when the phone has been charging and the phone is being not just hot, I'm talking boiling to the touch!
I have rebooted into recovery but....recovery img and boot img have disappeared. They have been present in recent weeks but for some reason they have disappeared.
I have reinstalled clockworkrecovery via ROM Manager a couple of times but there is still no change. TBH I'm sick of the issues I've had with the phone since rooted and it's not for me so plan on going back to stock whenever I can, however, I need recovery!
Can anyone point me in the right direction to sort this out and if possible not by plugging my phone into a PC. I am away with work and don't have my own computer for a while.
Thanks
Click to expand...
Click to collapse
its because you installed your recovery via rom manager. you want to reflash your clockwork recovery through fastboot so that it will stay permanently. look in the development section for instructions.
---------- Post added at 05:30 PM ---------- Previous post was at 05:29 PM ----------
AllGamer said:
you can always flash the boot recovery back into the phone, just follow any of the how to root guides
Click to expand...
Click to collapse
i got to say that youre the only xda mod, that i know of, that also helps out people with issues and not just xda/site stuff. thank you!

Thanks for your help guys.
I flashed the cwm recovery via fastboot and loaded up cm7 but each new ROM I used (that had been there previously) didn't boot into a fresh version, it had elements of the previous versions I had run such as MIUI (the clock), the Genexus S 2.0 drag and drop lock and wallpaper and some elements from The Infinity ROM. Very strange.
Prior to the latest mix up the phone had become very unstable, especially the touch screen and I am not exaggerating when I say the phone just wasn't usable. I even considered getting a BlackBerry Torch 9810!!! I mean wtf?!
Anyway, I have reflashed a stock nandroid backup via CMW and relocked the bootloader. I had a few permission errors but when I rebooted that seemed to go away. I'm now quite happy I'm back to standard because of the reliability issues I experienced.
When I reboot to recovery it comes up with a White box with an arrow coming out with the android at the side of it. Is this normal or should there be a standard recovery img? However, I have noticed if I press the volume up and power again it goes to a purple recovery screen with wipe cache partition, factory reset etc.
Also, all my ROMS and Titanium Backup files are still viewable from recovery, is that usual? Would I be ok to mount as USB and delete those individual files?
Thanks

When you switch roms you MUST wipe data factory reset, wipe cache, wipe dalvic cache. Then flash the new rom.
Sent from my Nexus S 4G using xda premium

[U8800] End of some Official 2.3 Bootloopings

I think I found out the cause of some bootloopings and its the "Log Switch" option in project menu.
When we try to root the rom and the the phone reboots:
A)if he reboots ok, you must go again into project menu (*#*#2846579#*#*) and "switch off" the Log.
Everyone tell us we must switch this thing on in order to root the phone but no one says that we should turn it off again after proccess completed....
B) if starts immediatly with bootlooping and never booted againd after the rooting proccess just take the battery out andenter into recovery (vol up + Power). Once there make a "Data factory reset" and reboot.
The phone will then start normally this time with no Bootloopings.
With luck you have SU installed and the phone is rooted.
If yes, just go to project menu (*#*#2846579#*#*) and "switch off" the Log.
If not just try the rooting again
But the major deal is the Log Switch.
Hope it helps anyone

I never had bootloops with 2.3 official rooted and log switch was turned on before and after

I'm happy for you!

Moved to General
Thought this may be helpful to some, it has no place in the development section.
Thanks for the contribution, i would usually close, but as it could be helpful, on this occasion i will move it.
Take it easy
O_G

yes don't close it please as I noticed that many had bootloop issues with these releases. I was one of them but this finished after switching the log of. In my caes that solved my problems.

I had thought that too but none of the combinations i tried worked.
I had tried switching off Logging,factory data reset,flashed again without rooting and after 2-3 days that everything seemed that worked normal and i had loaded all apps i wanted, bootloop appeared again and had to factory data reset again in order to use phone.
So i gave up and reverted to 2.2

I never had bootloops but if that's really what's causing it, that's a great catch!
Congrats!

well as I said with me, since I have done this the bootlooping stoped.
Before Everytime I reboot the bootlooping started and only stoped with a factory reset. Then I tried to switch Log Off again and not a single bootloop and more than 48 hours.
Flashed OC kernel, UOT Kitchen, etc etc and phone running perfect.
Look, I have flashed and tested this rom many many many times and alwas endup with bootlooping eventually. This did the trick for me and I consider it a major step as I can now use the rom freely and without being afraid.
As I said, is just 1 more Idea that people having this issue could try out and see if helps.
I just took the liberty of sharing this so that in case o dispair for some, they can have other alternatives.

Didn't help me, actually it did the opposite...my phone didn't boot loop until I went and touched the freaking "Log switch" option...should have let it ON...GRRRR....Got to taste Huawei's bad medicine again...or my own...I should have known; if it ain't broken, don't try to fix it!

lololol
Huawei's each one with own personality...

Druida69 said:
lololol
Huawei's each one with own personality...
Click to expand...
Click to collapse
Indeed!
Mine, for example, had precisely the opposite behaviour.
In order to root the phone, with the latest official GB ROM, i had to switch the logging to On. Otherwise i got bootloop with every ROM. I was also unable to root the official roms without logging On.
Well, at least it was coherent.
Question: When we flash a new ROM the logging is turned off by default, right?
If so, how can it influence negatively the ROM stability?

Druida69 said:
lololol
Huawei's each one with own personality...
Click to expand...
Click to collapse
Tell me about it.

SilveRRing said:
Indeed!
Mine, for example, had precisely the opposite behaviour.
In order to root the phone, with the latest official GB ROM, i had to switch the logging to On. Otherwise i got bootloop with every ROM. I was also unable to root the official roms without logging On.
Well, at least it was coherent.
Question: When we flash a new ROM the logging is turned off by default, right?
If so, how can it influence negatively the ROM stability?
Click to expand...
Click to collapse
You understand it opposite m8.
You must turn the Lon On to root the phone.
After root my advice is to turn it back Off again as it was from the beginning..

Ah ok, nevermind then. lol

my x5 dont have bootloop but this topic will help very people,thanks for the trick lol
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
driuda you have a theme of UOT Kitchen??? I make one for me but failed,please help me?i dislike stock theme is for children hehehe

at the moment I only used UOT this time to change the battery icon to battery percentage circular.
Its one of those must haves that I miss from official rom, the battery percentage....
Coking a theme is very easy. You just choose all the option you want and in the end upload the framework-res.apk and SystemUI.apk files and wait for the coking.
After that pick up the file and flash it with CWM.

mhh i dont think that the log switch is the only thing that causes bootloops.
first i installed 2.3.5 and a few hours later i switched the og on. The bootloops started.
So i had to do a factory reset...
Now after the reset I quikly turned off the log switch. but just a few hours later it started again bootlooping......
any other ideas? or do i have to go back to miui? when yes can i do the following?
: 1. factory reset
2. get root
3. install cwm
4. install my backup?

let me see if I understand.
You installed the latest official release, then you switch the log on? for what?
I assume you switch it on to root. Did you root it?
Yes yes you did well by turn it off as the log is off by default.
Next step should be installing the CWM 5.0.2.7.
Unfortunatly after bootlooping start only solution is factory reset which means having the phone all wiped again which is a pain after a few hours of putting it at our taste.
I think restoring a MIUI backup through CWM won't work.
I have tried this preocedure several times with MIUI or any other custom rom.
The correct way to go gack is downgrading to an official 2.2 release, then root it, install CWM, install a MIUI rom (in your case) doing all the 3 wipes. After you confirm that the rom was installed correctly and is working you can then go to CWM and restore a backup.

Druida69 said:
let me see if I understand.
You installed the latest official release, then you switch the log on? for what?
I assume you switch it on to root. Did you root it?
Yes yes you did well by turn it off as the log is off by default.
Next step should be installing the CWM 5.0.2.7.
Unfortunatly after bootlooping start only solution is factory reset which means having the phone all wiped again which is a pain after a few hours of putting it at our taste.
I think restoring a MIUI backup through CWM won't work.
I have tried this preocedure several times with MIUI or any other custom rom.
The correct way to go gack is downgrading to an official 2.2 release, then root it, install CWM, install a MIUI rom (in your case) doing all the 3 wipes. After you confirm that the rom was installed correctly and is working you can then go to CWM and restore a backup.
Click to expand...
Click to collapse
yes i did turn it on becuase i wawnted to prepare it for rooting but since im not at home since 3 days i cant.
But after the bootlooping i turned it off, but it bootlooped later again....
thank you for the intriductions!
edit: where can i find the 2.2 stock rom for germany? and how to install it? like 2.3.5?

levibuko said:
yes i did turn it on becuase i wawnted to prepare it for rooting but since im not at home since 3 days i cant.
But after the bootlooping i turned it off, but it bootlooped later again....
thank you for the intriductions!
edit: where can i find the 2.2 stock rom for germany? and how to install it? like 2.3.5?
Click to expand...
Click to collapse
if it is to downgrade and then move forward to any other rom, custom or not, you can use any version don't loock spexifically to a german one.
Here you have a list of stock rom:
http://forum.xda-developers.com/showthread.php?t=1167882
http://wiki.modaco.com/index.php/Huawei_Firmware_U8800 (MOdaco Wiki)
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8800_IDEOS_X5 (XDA Wiki)

[Q] Please help (ASAP)

So I recently received my nexus 4 device and was actually debating if i should root the phone or not... however I ended up rooting it and this device been working rock solid (I highly recommend any Android user to root their device to have access to unlimited customization). Few days later I decided to flash AOKP, and I did however during the boot up process after flashing AOKP screen was stuck in bootloop mode (unicorn screen that says Initiating Swagger at the bottom)... it kept going on for almost 30 minutes, until I decided I should reboot the phone.... after reboot is complete I now see that my phone is flashed with AOKP, its by far the best ROM I have ever used Period... however here comes the downside, i have almost half of my applications missing including Playstore and many other applications.... i tried fixing the issue by rebooting, formatting, wiping data and cache, nothing seems to get my applications back.
I have few questions I would like to ask...
1. has this happened with anyone before ?
2. is there a way to fix this error and get my applications back ?
3. should I unroot the phone, then root it again and flash AOKP or that would not help ?
any answer would highly be appreciated... thanks in advance.
i tried unrooting the device...
everything seems to be fine until i type in the command (./fastboot-mac -w update image-occam-jop40c.zip) i get the following... sending 'system' (531281 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
any suggestions ?

You have to flash the rom AND the Google apps package.
You can find it here:
http://goo.im/gapps/gapps-jb-20121212-signed.zip
Flash that in recovery after EVERY rom flash.

reply,
Thanks for the reply, I figured it could be the google apps package... If you don't mind am kind of naive when it comes to these stuff, would it be possible to tell me how to do it step by step ? Id be really thankful to you.
Ps. I have no clockwork recovery installed on my phone, and I cant seem to download anything with playstore missing

additional info
I can't seem to get into Recovery mode, every time I try to I get the android logo with the open chest and the red triangle in the middle, and it says ( No command) under it... any advice?

hanaii2 said:
I can't seem to get into Recovery mode, every time I try to I get the android logo with the open chest and the red triangle in the middle, and it says ( No command) under it... any advice?
Click to expand...
Click to collapse
That's the stock recovery. You need a custom recovery to flash gapps.
Boot into the bootloader and flash a customs recovery. Either cwm or twrp.
Sent from my Nexus 7 using xda premium

actually, dont flash the gapps after EVERY rom. some aosp roms like aokp and cm need the gapps flashed seperately. but many aosp and stock roms come with the gapps preloaded. just remember to read the whole original post and the directions to know what and how to flash and you probably wont run into problems like this again
---------- Post added at 04:10 AM ---------- Previous post was at 04:01 AM ----------
oh and to get clockwork mod recovery follow one of the how to stickies in one of the threads, general or development, about how to use the bootloader and fastboot (just google how to get the android sdk where you get all the things like adb and fastboot) and also how to get back to stock which can be very helpful. oh and i highly recommend one you get your rom flashed to download goo manager from the play store to install twrp, its way better than cwm. and for your rom i also recommend the codefirex rom, i find aokp to still be in its earlier stages and just be a little slower and less battery life than codefirex. another good rom is xylon, its also very smooth.

mbucks911 said:
actually, dont flash the gapps after EVERY rom. some aosp roms like aokp and cm need the gapps flashed seperately. but many aosp and stock roms come with the gapps preloaded. just remember to read the whole original post and the directions to know what and how to flash and you probably wont run into problems like this again
---------- Post added at 04:10 AM ---------- Previous post was at 04:01 AM ----------
oh and to get clockwork mod recovery follow one of the how to stickies in one of the threads, general or development, about how to use the bootloader and fastboot (just google how to get the android sdk where you get all the things like adb and fastboot) and also how to get back to stock which can be very helpful. oh and i highly recommend one you get your rom flashed to download goo manager from the play store to install twrp, its way better than cwm. and for your rom i also recommend the codefirex rom, i find aokp to still be in its earlier stages and just be a little slower and less battery life than codefirex. another good rom is xylon, its also very smooth.
Click to expand...
Click to collapse
the main reason I use AOKP is that it allows me to disable the navigation buttons and with fullscreen view on a device like nexus 4 especially after you get the screen color fixed with (nexus 4 display control) this is a TRUE BEAUTY. I replaced the navigations buttons with LMT, i find it highly functional and stylish.
Am thinking I should return the phone back to stock, then start all over again to avoid all errors, only issue is I have no idea how to return it to stock.... tried using mac and pc but both wasn't working properly... I guess am missing something here. Any recommendations ?

If rooted, download Rom manager, open it, flash custom recovery. Boot into recovery after install. Touch install zip from sdcard, flag GAAPS zip file and reboot phone .
There you'll have the Google apps package now.
Sent from Nexus 4

[Q] How long for first boot after flashing rom???

Hi there,
I really hope I haven't ruined my son's Galaxy Y.
I've followed all the instructions from several different threads and have just "flashed" an new rom (Cyanogenmod 7) onto it and I'm now sitting here with it switched on but only the front screen (saying Samsung Galaxy). It's been like it for 10 minutes. Should it take this long??
Feeling a bit sick that I've ruined his phone for him rather than making it better.
J

yellowplanet said:
Hi there,
I really hope I haven't ruined my son's Galaxy Y.
I've followed all the instructions from several different threads and have just "flashed" an new rom (Cyanogenmod 7) onto it and I'm now sitting here with it switched on but only the front screen (saying Samsung Galaxy). It's been like it for 10 minutes. Should it take this long??
Feeling a bit sick that I've ruined his phone for him rather than making it better.
J
Click to expand...
Click to collapse
It usually you get a bootloop . Flash via odin and try to reflash the rom

GalKill said:
It usually you get a bootloop . Flash via odin and try to reflash the rom
Click to expand...
Click to collapse
Do you know a good ODIN set of instructions I can follow?

can I use odin if the phone is in this state? Does it work from the laptop?

yellowplanet said:
can I use odin if the phone is in this state? Does it work from the laptop?
Click to expand...
Click to collapse
You can still enter download mode by pulling out the battery and hold volume down and home and power button
Here the link to firmware : http://forum.xda-developers.com/showthread.php?t=2568853
Credits to marcussmith2626

what do you mean pull out the battery? Do you mean take it out and then put it back in again?

yellowplanet said:
what do you mean pull out the battery? Do you mean take it out and then put it back in again?
Click to expand...
Click to collapse
Yes. Because in bootloop you can't turn off your phone, isn't it?

trying to install drivers now. I'm so annoyed with myself for trying to do this

now it wont recognise it by usb even though i've installed the drivers!

yellowplanet said:
Hi there,
I really hope I haven't ruined my son's Galaxy Y.
I've followed all the instructions from several different threads and have just "flashed" an new rom (Cyanogenmod 7) onto it and I'm now sitting here with it switched on but only the front screen (saying Samsung Galaxy). It's been like it for 10 minutes. Should it take this long??
Feeling a bit sick that I've ruined his phone for him rather than making it better.
J
Click to expand...
Click to collapse
Just flash the stock rom via odin and your phone will be fine , then u can relax and look for a good custom rom and check what went wrong when you flashed the cm7
---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------
yellowplanet said:
now it wont recognise it by usb even though i've installed the drivers!
Click to expand...
Click to collapse
Just remove the battery , restart you laptop and try again ..
Watch this for more info : http://www.youtube.com/watch?v=8SGqQl321RE

it might have worked!!!!

ok, so i managed to get it to install back to factory settings using odin. now i know that works, do I simply use odin to flash a new rom or do i need to do other things first?

well i thought everything was back to normal but its now doing a software update and seems to be stuck at 86%
oh actually its moving again now

yellowplanet said:
ok, so i managed to get it to install back to factory settings using odin. now i know that works, do I simply use odin to flash a new rom or do i need to do other things first?
Click to expand...
Click to collapse
U cant flash a custom rom like that from odin , Follow instructions correctly in the rom's description that u are trying to flash.
Hit thanks if i helped
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
yellowplanet said:
well i thought everything was back to normal but its now doing a software update and seems to be stuck at 86%
Click to expand...
Click to collapse
What software update? OTA? the one u do direrly from ur phone? I dont see why u need to do that if ur gonna flash a custom rom.. since now its stuck just be patient and wait if it dont work den try to remove d battery and reboot..

What rom are you trying to flash??

original reason for trying to do this was because the internal memory on this phone is awfully low. I was going to try to allocate some of the sdcard to it.
Having never done anything like this before I've had to read through lots of different threads to try to feel confident enough to try.

yellowplanet said:
original reason for trying to do this was because the internal memory on this phone is awfully low. I was going to try to allocate some of the sdcard to it.
Having never done anything like this before I've had to read through lots of different threads to try to feel confident enough to try.
Click to expand...
Click to collapse
Stock Rom is always be the best one
Btw, I never get same problem like you when flashing

but i'd like to get rid of all the unwanted apps from the stock rom

yellowplanet said:
but i'd like to get rid of all the unwanted apps from the stock rom
Click to expand...
Click to collapse
Use rom toolbox pro (paid) in playstore to uninstall unwanted system apps. But, don't try to uninstall apps that you don't know what it used for

yellowplanet said:
but i'd like to get rid of all the unwanted apps from the stock rom
Click to expand...
Click to collapse
install link2sd (playstore)
you can use that app to uninstall system apps[
note to uninstall system apps you need to be rooted
---------- Post added at 07:17 AM ---------- Previous post was at 07:13 AM ----------
yellowplanet said:
Hi there,
I really hope I haven't ruined my son's Galaxy Y.
I've followed all the instructions from several different threads and have just "flashed" an new rom (Cyanogenmod 7) onto it and I'm now sitting here with it switched on but only the front screen (saying Samsung Galaxy). It's been like it for 10 minutes. Should it take this long??
Feeling a bit sick that I've ruined his phone for him rather than making it better.
J
Click to expand...
Click to collapse
did you convert your system to ext and install the common kernel for cm7?
if you just flashed the rom it wont boot without doing the above
cyanogenmod roms (cm7/9/10/11 etc) require you to be on an ext system partition
stock roms use rfs partition so you need to convert your system partition to ext
you also need a kernel that can boot ext partitions (stock kernel can only boot rfs)
therefore you also need to flash Bieltv.3 kernel
my instructions for installing cm7 are
http://forum.xda-developers.com/showpost.php?p=50907846&postcount=25
and the meta-inf folder mentioned you can download from
http://forum.xda-developers.com/showpost.php?p=50908670&postcount=27
if all else fails simply flash stock rom via odin which links to the firmware and guide are in my signature

All roms brake my phone..?

So I have tried a lot of roms on my note 3 and I have to say most of them are awesome.. I just did the Eclipse rom today - fantastic.... I want it to be my daily driver actually.
But a problem that I have on ALL roms that I use is, when I go to power off or reboot the device it sits at a "Shutting down" screen likes its closing apps, and getting ready to shut off. The problem is, even after an hour - it doesn't do anything.. I have to pull the battery.
I have tried 6 or 7 roms and they all do the same thing.. This is using safe strap. Each time I have deleted and recreated the slot for the rom.

janderson2k said:
So I have tried a lot of roms on my note 3 and I have to say most of them are awesome.. I just did the Eclipse rom today - fantastic.... I want it to be my daily driver actually.
But a problem that I have on ALL roms that I use is, when I go to power off or reboot the device it sits at a "Shutting down" screen likes its closing apps, and getting ready to shut off. The problem is, even after an hour - it doesn't do anything.. I have to pull the battery.
I have tried 6 or 7 roms and they all do the same thing.. This is using safe strap. Each time I have deleted and recreated the slot for the rom.
Click to expand...
Click to collapse
Are you using the stock ROM slot?

janderson2k said:
So I have tried a lot of roms on my note 3 and I have to say most of them are awesome.. I just did the Eclipse rom today - fantastic.... I want it to be my daily driver actually.
But a problem that I have on ALL roms that I use is, when I go to power off or reboot the device it sits at a "Shutting down" screen likes its closing apps, and getting ready to shut off. The problem is, even after an hour - it doesn't do anything.. I have to pull the battery.
I have tried 6 or 7 roms and they all do the same thing.. This is using safe strap. Each time I have deleted and recreated the slot for the rom.
Click to expand...
Click to collapse
And what version of Safestrap are you running? The current is 3.75 B04. 3.72 did not support extra rom slots without a bit of tweaking. But it would always hang at shutdown, so you had to pull the battery to restart it. It is now fixed with the current build of SS.

strider5236 said:
And what version of Safestrap are you running? The current is 3.75 B04. 3.72 did not support extra rom slots without a bit of tweaking. But it would always hang at shutdown, so you had to pull the battery to restart it. It is now fixed with the current build of SS.
---------- Post added at 11:09 PM ---------- Previous post was at 11:08 PM ----------
Sorry : Delete
Click to expand...
Click to collapse