I did a factory reset on my Virgin mobile Kyoceria Rise which i have done before, but this time something went wrong. The phone just continues to BOOT LOOP after it gets to the "flick to unlock your phone screen"
So it does boot into the OS.. just it reboots soon as the stock flick to unlock screen comes up. The only thing i changed with this factory restore is i froze/deleted some bloatware a couple months ago that i didnt restore before the trying a system restore on monday. Im wondering does this have anything to do with it or did something else get screwed?
I know i froze Virgin mobile setup which might be the issue, but i doubt it.
I already read there is no custom recovery for this phone and no clockwork because Kyocera has the bootloader locked down pretty good, so if something goes bad you have to send it to them or just get a new phone.
Also, i already tried the android restore by holding the volume down+power key and a selecting full data reset/restore but this still results in the same bootloop. Also says, "Cannot find /misc" which is normal i read.
Just wondering if my $50 android gone?
EDIT: i dont see a section for this phone so hopefully this is right.
I spent 3 weeks trying to fix my Rise which was also in a boot loop. I've looked everywhere and still havnt found a solution.....until kyocera agrees to unlock the boot loader we got paper weights but for me this was a great learning experience! I taught myself how to use adb and SDK. I have a Motorola Xoom and ive rooted it, bricked it, and unbricked it! I recently started looking around again for a solution to my Rise.... I have the stock image but I can't push it to the phone. I put my rise in recovery mode connect it to my PC but adb won't recognize it. So our best bet is hope that the boot loader will someday be unlocked......
Sent from my Xoom using xda app-developers app
Related
Hey all,
I did my searching for the last several hours, and am feeling pretty weak. I know there are several other posts with this error - but please let me explain my situation.
Phone was running 2.3.6. I am unsure how it was originally unlocked (carrier unlocked) and bought it used. To my knowledge it did not have root access... (though the advert said it did - running SU in Terminal to show if it had access failed)
I tried doing a factory reset on the phone because it kept acting weird. Just rebooting 10 times a day, and wifi not working either.
Since the reset the phone has not made it past the M Dual Core screen.
Edit as I type: As I type this, I FINALLY got into recovery mode. It took a long time... is that normal? I mean.. loongggg. Now i see other posts state I just need to click the bottom right corner above the search key and I should be on the way to recovering the device...
This however is not working...
I will keep the phone plugged in over night and see if it just needed more time I suppose. Can you guys recommend anything?
I am on win7 - should have the device drivers installed (though, Windows doesn't seem to recognize this with a notification bubble). I know the phone was not on USB Debug Mode when I clicked 'factory reset'.. would it have retained this?
I will update as i have more information.. otherwise if I am missing something please let me know.
Thanks again,
-k
Try booting into recovery mode by holding volume down while turning on. When the menu appears keep pressing volume down until it says android recovery and then press volume up to select it. If an android Guy with a warning sign shows up, press volume down and up. A menu should appear soon. Try to do a data wipe and factory reset from there.
Sent from my MB860 using XDA App
Hi ar31791, thank you for the reply.
That worked to put me into a recovery mode - very nice. Is the button combo different depending on the version of android your'e running, or just phone dependent? I appreciate that.
Couple follow up questions if you guys don't mind and can help
- after the factory reset - my boot time is incredibly slow.... like 30 minutes to boot kinda thing. I tried to factory reset several times since, and its the same issue.
- my data is not working on the phone. I used the apn suggestions from all sites I've found, rebooted (took a while) tried data roaming, etc, but it just doesn't work. I have a decent idea that the apn's are correct because the mms apn worked fine with a test picture message.
My main concern is the incredible lengthy boot time and the data no longer working. The issue with wifi still showing 'error' when enabling it was not resolved by the reset (I didn't think it would - I was reading other posts where it is suspected as a hardware issue).
Thanks again for the reads, and replies. I appreciate the help!
-kenny
You need romracers or cwm. Unless yer going to stay stock.
Sent from my MB860 using xda premium
Is this an att or a rogers/international phone? Best bet would be to flash pudding and than cwm + custom roms
hey again- thank you for the replies.. seriously. much appreciated.
phalanx, i dont mind staying stock but would that not allow the data connection to work correctly? i found a few posts based on the romracer. i lack the hands on experience, but it looks like i just need to follow the steps for an adb push and then install eh?
you mention staying stock, is that an option? info on my setup below
crnkoj, i am running a bell phone on a fido network in canada. bought on ebay pre unlocked. i do not bekieve it is rooted. phone, mms and text work fine, it seems to be a problem finding a data network at this moment.
thanks again guys, ill be taking a look into the tutorials for romracer and cwm, and giver a shot. lemme know if you have any further ideas, questions or anything you think i might need to know.
edit.. also, whats the deal with the crazyyyyy long boot up time?
kenny
(send from a mobile.. please excuse any typos or punctuation errors)
No its just that with an unlocked bootloader you can flash a new.recovery and that makes it easier to flash roms and also kernels and radios. Kernels and radios can affect your ability to connect with data and can even affect the speeds.
Sent from my MB860 using xda premium
I had a similar situation. So, i did a full wipe installed the rom did another full wipe then installed the appropriate kernel and booted it up. I believe you nedd to install the right kernel per the instructions. It will mot boot if the kernel is not correct.
Sent from my MB860 using xda premium
Thanks again guys,
Man it's a funny issue. I am always able to get in and factory wipe the device, but it seems that sometimes that damn M screen will sit forever. I left it over the course of a movie and a half (probably 3 hours) and that screen was still just sitting there.
I get into the fastboot menu easy enough before that screen hangs, and sometimes i can get into the Boot Android (without BP) (I believe it's called) and sometimes it hangs, and sometimes it works.
Other times, like right now, it boots just fine and kinda fast.
I am having an issue with the RSDLite application recognizing my phone. It did once - then hung at 94% flash of the pudding tutorial. I didn't realize the tutorial says to keep the phone plugged in for 10 minutes even after a fail to see if it actually completes. I havent been able to have the software recognize the phone since- I've installed and reinstalled the motorola drivers, set the phone to usb debugging, and was able to try 2 computers, and 2 different cables. I'll giver another shot though.
I am pretty sure my boot loader was unlocked (as I said I had this all done from an ebay purchase) so I think I can just proceed to the flashing, but if there is a way to confirm that it is indeed locked, I'll take the advice.
The more I read though, it looks like I might just need to send this beast in for a service call with Motorola, because of that damn wifi "error" error. I'd hate to go through all this and realize it still will not work.
Thanks for the replies, I'll always take more suggestions, and if you guys think I'm on the wrong path, let me know. I'll keep searchin dem' forums
If your bootloader is unlocked it will say unlocked in white letters on that M boot logo screen. Did you run "fastboot oem unlock" after the rsd flash?
Sent from my MB860 using XDA App
I've been searching the forums, and google for a while and can't seem to find a solution that works at all for me. First off, a little history. I am a n00b, and I very stupidly rooted my phone last night, without a recovery.... Actually I don't think just rooting was a big deal, it was me changing the vm heap properties that was really stupid. Why did I change it when the phone was working fine you might ask? Because I quickly gleaned over a forum post about adjusting the heap size to make your phone blazing fast, so, like any other idiot would, I did what the thread suggested, and instead of blazing fast speeds I got a boot screen logo....... forever... Talk about a huge mistake on my part....
Here's the problem,
Phone is stuck on the bootscreen, I can boot into system recovery (stock).
Android System Recovery has a message on the bottom of the screen that says "E: Cannot load volume /misc!"
I have wiped the cache partition, and did factory reset according to the manufactures website.
I cannot get ADB of Fastboot to see the device, even with drivers installed.
I do have a back up of build.prop that is unscathed, but I have no idea how to flash it, or "push" it or whatever.
I do not have CWM installed, and it appears that usb debugging is disabled.
My phone is a Kyocera Hydro. I'm using Windows 7 64bit.
I know I should never have done this, it was idiotic, and easily the dumbest thing I've done in a while. I'm hoping someone out there can help me fix this. Is it possible to put the backup of build.prop on the SD card and have it overwrite the corrupted one? Is there any hope at all?
I guess it can't be done then? I had hoped that as long as the bootscreen could come on that there was hope. Hopefully someone out there knows how to push the backup build.prop back onto the phone.
Well right now you're pretty screwed. There's no way to restore it without a custom recovery. You have 2 options -
1) Wait for someone to make a custom recovery for your phone.
2) Try to claim warranty and get it restored/exchanged at the service center. Say it just randomly rebooted and got stuck at the boot screen.
Sent from my Desire HD using xda premium
Aravoth said:
I guess it can't be done then? I had hoped that as long as the bootscreen could come on that there was hope. Hopefully someone out there knows how to push the backup build.prop back onto the phone.
Click to expand...
Click to collapse
Where did you get the phone Boost, Amazon Wal-Mart?
Sent from my KFTT using xda app-developers app
I'm new to xda-developer.com, eh.
I own a AT&T ZTE Radiant Z740 GoPhone.
First of all, I did not make any kind of back-up. I don't even have ClockworkMod installed or any kind custom recovery.. I factory-wiped it, cleared cache, and literally went though every option on recovery mode. Under one circumstance, I rooted it. It's completely stock with root on it.
This happened when I was cleaning my phone because memory was almost full and I literally ended up deleting a portion of OS itself... ( ./system files) I assume that made it corrupt and froze my phone which I had to pull battery out and back. The phone rebooted to a familiar AT&T logo screen then screen went black for brief moment. Then AT&T logo went back on. Then the phone itself automatically went recovery mode with a dark scene which revealed a dead green droid lying on invisible floor in the background with its chest 'door' open allowing me to see bluish subject in his body and the red triangle suspended in the mid-air.
I tried every option, desperately.
Trying to boot it in fastboot with VOLUME DOWN + POWER didn't work for me. Apply update from ADB doesn't let me do anything more than 'kill server', 'start server', 'adb sideload <file>'. Maybe there's more, but far as I know, most commands will respond with 'error : closed'.
I did enable USB debugging before the soft-brick, but factory-wipe might deleted that setting. That maybe... maybe.... just maybe... explain why I keep getting 'error : closed'. :crying: If this problem wasn't in front of me.. I probably would have restored my phone sooner.
Fastboot seems like my only remaining option to recovery of this phone. But I can't get in fastboot. 'adb reboot' command doesn't even work for me.
I'm waiting for the inevitable answer... that I'm screwed. Any help would deeply appreciated.
Picture of my phone in recovery mode is in the attachment. --- You can see, that I've desperately attempted to sideload stock ROMs for this phone and got a failed error.
bump
Does power + vol up bring you to download mode (black screen with boot loader on top) ?
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
L1ght3d said:
I'm new to xda-developer.com, eh.
I'm waiting for the inevitable answer... that I'm screwed. Any help would deeply appreciated.
Click to expand...
Click to collapse
Old post, but you are not screwed, the bootloader is still fine, just follow the instructions here http://androidforums.com/threads/zt...s-kernel-source-and-other.828110/#post6437794
and you are good. Once you are done unbricking, I would suggest you sell yours on amazon, they are worth about $80 USD and you can get a much better phone with that money
I have been reading everything I can find and tried to figure it out myself but the more I read the more questions I have and the less sure I am about trying any of the things I have read.
My problem is with an lg tribute from the company called Textnow. My friend ordered the phone from them and was having some issue she decided to try to fix by doing a factory reset which caused it to be stuck on the Lg boot logo. I tried booting to recovery to fix it. The recovery was TWRP. I was under the impression that Twrp was a custom recovery program that was installed after unlocking boot loader. Best I can tell is the phone was already rooted by the company. Does this sound right?
I messed with it for while but couldn't get anywhere with it because I haven't any knowledge of rooting except what I read . I noticed it kept saying something about simulating actions and figured that out but now after trying to back up and restore and poking around that it says there is no os , I was hoping someone could help me figure out where to go from here as it isn't my phone and I would hate to damage it although my friend keeps telling me to just try whatever no big loss because she can't use it like it is so.
I am not sure what the phone had for firmware because I cant get it on. I only know that it had twrp 2.8.5.0 as recover not the usual android. I can access the phone internal and external through twrp and though pc and adb. I made sure to get drivers updated. I tried to flash the stock rom from its forum but it failed,. any info would be mush appreciated
Okay so my phone randomly rebooted 2 days ago and when it got to the LG logo screen it froze. I tried to hard reset it, i went in to the hard reset menu clicked yes once then confirmed the hard reset by selecting yes a second time and the phone froze on highlighted yes. I have pulled the battery and tried to do this multiple times to no avail. So next i went to my PC and started google searches. Often i found things such as being stuck in boot loop which my phone wasn't, it was just frozen at the LG logo screen. Regardless I like to think of myself as self educated tech savvy (which now from reading all of your posts im not, im not even a little bit, in fact im tech stupid.) I did follow post through to the LGUP tool and downloaded a stock KDZ and got my phone into download mode>firmware update screen, i was able to get al the correct drivers and get LGUP to recognize the device and i loaded the stock KDZ and tried to do a Complete wipe reinstall. The program as able to interact with my device and went through the process, i thought i had fixed my phone. After a fresh install(or what i thought was a fresh install) i rebooted after the update and went to the LG logo screen and froze. The only difference is now when my phone starts, right before the LG logo appears i get the green android robot with what looks like open working "guts" real quick before it goes to the Logo and freezes. So back to the drawing board and i wanted to attempt some of the things ive seen like TWRP recovery etc but here i am getting lost. Forgive me if im posting things that have been answered but i keep getting confused. I dont know what the difference is between fastboot boot loader recovery mode or any of that is. also i kept noticing time and time again that my phone has to be in USB debugging mode and i dont know if it is. I cant turn my phone on to get it into USB debugging mode now anyways. Im okay with my warranty being voided and im okay with rooting if thats what i have to do to make it work. I have installed ADB and fastboot and some twrp recoveries etc but im clueless. Lastly know that i never Rooted my phone or anything but i was a torrent downloader. forgive me im triyng to provide as much information as possible.
PLEASE NOTE - I had to sign up to post here obviously and i loved how it said if you have an IOS go buy an android and come back LOL
Message Tung Kick. He can get u out of any thing
Hit thnx if this helpd