Noob here, one of the kids nabi2 has pooped itself. System software crashes constantly "if" it boots normally. No recovery options work, the kernel recovery brings up sick android, forced recovery just blanks screen and goes no where. Fastboot has nothing i can use...
Ive tried so many places with all sorts of advice, and recovery directions IM STUCK !!!
Is there a way to boot a recovery image of sdcard ??
Please help!!
Blobbyknobby said:
Noob here, one of the kids nabi2 has pooped itself. System software crashes constantly "if" it boots normally. No recovery options work, the kernel recovery brings up sick android, forced recovery just blanks screen and goes no where. Fastboot has nothing i can use...
Ive tried so many places with all sorts of advice, and recovery directions IM STUCK !!!
Is there a way to boot a recovery image of sdcard ??
Please help!!
Click to expand...
Click to collapse
Did you look at general information thread? It has a lot of tools to help.
Related
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
You should reflash your recovery to TWRP using fastboot. Then boot into recovery using fastboot. From there you should be able to do a complete wipe and flash a ROM. It is outlined in the thread you linked OP and second post. Feel free to come into the d3rp q+a thread in my sig if you need more help.
It worked thanks you
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
unomillionaire said:
It worked thanks you
Click to expand...
Click to collapse
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
joeykrim said:
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
Click to expand...
Click to collapse
So you mean, stuck at the splash screen(HTC with white screen) and reboot again and again is because of the recovery destroyed? My phone stuck at the splash screen for about 10 seconds and then reboot again and again. I have tried to flash many recovery images, includeing twrp 1.0.3, twrp 1.1.1, cwm-1.0.4, cwm-1.0.5, cwm-5.0.2, all failed to boot up into recovery:-(
Thanks in advance!
So I've got stuck in a boot loop twice now (both messing with build.prop I'm pretty sure) and each time I couldn't get into recovery either. I held power + volume up + home and I saw the sammy logo come up (and in the upper right hand corner in blue there was 'booting recovery' for a split second)... and then nothing. I could get into download mode though.
Both times I freaked the **** out. The first time i boot looped like this I flashed the insecure boot image and cwm recovery via Odin/S3 toolkit again (it was a shot in the dark and I was scared) The phone still didn't boot (obviously), and i thought i still couldn't get recovery for a while but then it magically came up after a few tries. I attributed it to dumb luck.
The second time i boot looped, i still couldn't get into recovery. I tried flashing like before via Odin, and this time CWM came up as expected and I could restore a nandroid.
So if you get in a bootloop and your recovery isn't working (no idea why this happens either, any thoughts???) then go ahead and flash the recovery again via odin.
Maybe I'm pointing out the obvious, and if so give me the newb damnation i deserve. But if I helped hit thanks so maybe one day ill have the privileges to bug devs in the development forums (kidding about the bugging part ). I know I couldn't find info like then when I was searching (I was also in a state of panic). Maybe there should be something like this in one of the pinned threads in the dev forums.
Crap, i mean to post this in General. Buuuut it sort of fits Q&A too. Do as you see fit, mods.
andham95 said:
So I've got stuck in a boot loop twice now (both messing with build.prop I'm pretty sure) and each time I couldn't get into recovery either. I held power + volume up + home and I saw the sammy logo come up (and in the upper right hand corner in blue there was 'booting recovery' for a split second)... and then nothing. I could get into download mode though.
Both times I freaked the **** out. The first time i boot looped like this I flashed the insecure boot image and cwm recovery via Odin/S3 toolkit again (it was a shot in the dark and I was scared) The phone still didn't boot (obviously), and i thought i still couldn't get recovery for a while but then it magically came up after a few tries. I attributed it to dumb luck.
The second time i boot looped, i still couldn't get into recovery. I tried flashing like before via Odin, and this time CWM came up as expected and I could restore a nandroid.
So if you get in a bootloop and your recovery isn't working (no idea why this happens either, any thoughts???) then go ahead and flash the recovery again via odin.
Maybe I'm pointing out the obvious, and if so give me the newb damnation i deserve. But if I helped hit thanks so maybe one day ill have the privileges to bug devs in the development forums (kidding about the bugging part ). I know I couldn't find info like then when I was searching (I was also in a state of panic). Maybe there should be something like this in one of the pinned threads in the dev forums.
Click to expand...
Click to collapse
I apologize if this is in the wrong place, and I've really tried searching around, but nothing seems to work/ is tailored to the m8.
So, I just got an M8 new out of the box, rooted it and successfully installed cyanogenmod. Problem is, I was playing around with it, trying to get the GApp store and somehow (did what i think was) deleted my roms completely. Now upon booting up the phone I just get the "This build is for dev..." screen, and with the volume down+Power button to access recovery mode I constantly get put back to the fastboot screen. I tried flashing a custom recovery as in "Phone arena CWM flash recovery" guide, but no luck because my computer is reading the device as offline. I honestly have no idea what to do, and if anyone could help me I would be so greatful...
TL;DR: Stuck on boot screen, can't enter recovery mode, think i deleted all my roms, help please
On a scale of 1 - bricked, how bricked is my phone?
HUGE DEVELOPMENTS, GUYS! I've been able to access recovery mode again by re-flashing ClockWorkMod.
ctran1 said:
On a scale of 1 - bricked, how bricked is my phone?
Click to expand...
Click to collapse
On that scale, you are zero. If the screen comes on, you aren't bricked.
Hey guys i got a slight problem.
I had the Android Revolution HD Rom and i was trying to install another one , it really wasnt my first time doing this however this time a problem occurred.
My volume side buttons are not working so i couldnt get into recovery mode using them also on top of that the rom itself didnt have the option to go to recovery when turning off the phone.
I downloaded the Quick boot tool apk from Playstore and used it to go to recovery... I WISH I DIDNT
now my phone when turned on shows samsung logo and it goes to recovery and quickly goes back to the logo and loops in that way...
Is there anyway to access the download mode without pressing them sidebuttons, i even tried ODIN but it cant recognize the phone because it keeps looping...
I am clueless now and any help would be appreciated.
Sorry for spelling or any typos i am really angry atm.
alioni said:
Hey guys i got a slight problem.
I had the Android Revolution HD Rom and i was trying to install another one , it really wasnt my first time doing this however this time a problem occurred.
My volume side buttons are not working so i couldnt get into recovery mode using them also on top of that the rom itself didnt have the option to go to recovery when turning off the phone.
I downloaded the Quick boot tool apk from Playstore and used it to go to recovery... I WISH I DIDNT
now my phone when turned on shows samsung logo and it goes to recovery and quickly goes back to the logo and loops in that way...
Is there anyway to access the download mode without pressing them sidebuttons, i even tried ODIN but it cant recognize the phone because it keeps looping...
I am clueless now and any help would be appreciated.
Sorry for spelling or any typos i am really angry atm.
Click to expand...
Click to collapse
You can use Android Debug Bridge (ADB) to enter whether download mode or recovery.
josephiskandar said:
You can use (ADB) to enter whether download mode or recovery.
Click to expand...
Click to collapse
I will try this and get back to you.
Thanks
josephiskandar said:
You can useAndroid Debug Bridge (ADB) to enter whether download mode or recovery.
Click to expand...
Click to collapse
Did everything and it still does the same loop, from logo to partially loaded recovery and back...
alioni said:
Did everything and it still does the same loop, from logo to partially loaded recovery and back...
Click to expand...
Click to collapse
It doesn’t sound good then. Please read again threads like this on how to recover from a bootloop. If you really can’t access neither recovery or download mode using adb, that’s out of my knowledge, and you might need to read about how to fix a hard brick. There’s a thread about that in these stickies.
josephiskandar said:
It doesn’t sound good then. Please read again threads like this on how to recover from a bootloop. If you really can’t access neither recovery or download mode using adb, that’s out of my knowledge, and you might need to read about how to fix a hard brick. There’s a thread about that in these stickies.
Click to expand...
Click to collapse
i managed to get into download mode however prior the brick i didnt enable developer mode on the phone and now the pc cannot recognize it when connected.
Developer switch is irrelevant to download mode, search the many threads on things to try to get Odin connected.
Hi guys, I really need your help.
I'm new at this rooting stuffs and I tried to root my Oppo Neo 5.
I tried so many softwares like OneClickRoot, FramaRoot, and Kingroot but none seemed to work.
So I resorted to an app called oppo tools
It worked at first but I got really annoyed when my status bar suddenly colored to red when my phone discharges to 15% so I unrooted my phone and rooted back again. I really thought that was going to fix my problem but that's where the bootloop issue started.
I tried to flash some custom recovery zip but it failed since I only have a stock recovery.
But the thing is, I found a guide that says to rename the clockworkrecovery img to PG86IMG.zip.
So I did tried that and as soon as I flashed the zip from my stock recovery, my phone hanged.
I long-pressed the power button to restart and boot into recovery mode but nothing seems to happen.
I'll try to explain a bit more on how it looks when I boot my device.
When it boots normally (I mean not pressing the volume to enter recovery mode) it will only show the logo but when I try to go into recovery mode it will show the logo with a little text on the lower left portion "Recovery Mode"
Before I flashed the PG86IMG.zip, recovery mode was still working and the charging screen when off is working too.
but after I flashed the zip, every time I try to recovery mode the logo shows up with the little text but RECOVERY MODE isn't working. When I charge my phone it automatically boots up and shows the logo and text like it's trying to go recovery mode (I'm just trying to charge? It's going to recovery mode)
I tried using "adb devices" on cmd but it's not detecting any devices.
I'm really out of ideas guys, I know not all people use this model but what would be your suggestion?
A suggestion on how to fix this would really be appreciated :good:
I'm sorry I'm really new at this, please correct me if I did something wrong starting this thread. :angel:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Salman Al-Badgail said:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Click to expand...
Click to collapse
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
DeepBricked said:
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
Click to expand...
Click to collapse
You made a soft brick, not to worry flash it with correct stock firmware, if the phone is in warranty than ask them to do flash, this will take approx 10-30min. If it isn't in warranty than you should try it own or else pay some amount and the rest they will do.
Salman.
how about bootloop, cant enter recovery, reboot continiously when turn on even going to recovery, only fastboot isnt rebooting automaticaly but pc days drivers not succesfuly installed, and when off it qont detect by pc because of rebooting auto,
where can i find a rom for my oppo neo 5
pls help me pls