Hello there. I am sort of a noob at rooting phones, this zte reef was my third successful root(or so I thought) of prepaid virgin mobile cheapies. I mainly root to remove and replace the obnoxious VM boot animation on startup--anyone who has owned one of these knows it can wake the dead, and will likely be the root cause of the zombie apocolypse sometime in the near future. I also remove a bit of google bloatware that, as far as I can determine, nobody on the planet actually uses--none of the fancy custom roms and whatnot, and replace the launcher with my beloved Nova.
Anyhow, being a silly noob, and having no prior issues with my previous devices, I did not save any sort of backup this time around, did not install CWM, and carried on as usual. Phone worked fine for several weeks. Then last night I fell asleep with it in my pocket. Battery died overnight as it tend to do in these situations. I awoke, plugged it in, charging screen pops up as usual. Hour later I try to turn it on and after being greeted by the android splash logo......blank screen.
Rebooted. Same result. Rebooted in android system recovery, wiped some things, reboot. Same result. Hard reset, still nothing.
Cannot find ANY rom compatible with this device, much less the stock one. ZTE of course will not provide me with any help. ZTE Reef N810 Virgin Mobile
So here is my question--does anyone have the stock rom for this device? Or is there any other way I could perhaps build a update.zip with the core apps that the system would allow to be installed from recovery mode(I suspect the launcher replacement may have destabilized the system, although why it waited this long to collapse is beyond me).
Throw anything you think of out there, I will try anything and have plenty of time to toy with it. Have to go to the library for computer access, but have access to another VM phone(unfortunately running 4.4 dangit)
Also am able to boot it into Field Test Mode, not sure if that could be used to communicate with the device in some way? Trying to cover all possibilities.
Thank you for reading, and btw xda your forums are, in a word, awesome. Well played!
ZTE REEF
Found anything yet?
Related
I bought an LG Mach LS860 (4.0.4 Ice Cream Sandwich) about a week ago, and I just found out about rooting. (This is my first Android.) I had no luck last night, but I tried today and I got it rooted.
Anyway... here's the problem: I was altering some settings with an app (I believe it was called Pimp My ROM.) and everything was fine. When I restarted, the battery was lower by about 7%. I figured the changes I made were the reason for this, so I went back and reverted them. However, when I restarted the phone this time, it wouldn't get past the boot screen. It would flash the Boost logo, go dark, then flash it again with an animation and a short vibrate. That's all. So I tried restoring the factory settings. (Volume down + power button, then power button and power button.) The phone went through and reverted settings, then rebooted. But THIS time, I got messages popping up like "Unfortunately, System UI has stopped." I believe there was something along the lines of "Unfortunately, Home has stopped." as well. On a layer below that at the bottom of the screen, there was another type of error. I think it had to do with voicemail. After the phone sat there for a bit as I looked online for a solution, the phone restarted again. Now it just goes to the problem from the beginning with the boot screen. My computer makes a noise indicating the USB is connected, but all my phone does is charge off it.
Any help would be much appreciated.
It's not necessarily that I'm inexperienced. I've done all sorts of flashing and things on PSP. Obviously Android is much more complex. But I know that it's not bricked unless it won't turn on at all. Because that's not a brick.
There's also very little (if any) development for this specific model. No one cares about the LG Mach because there are much more well-known phones. But I digress.
Please help. I'm extremely desperate to get this working again.
EDIT: I recently thought of another question. Would the hard reset erase all evidence of the root access? Considering I just bought the phone, I might be able to send it back. But obviously if they know I accessed the root, the warranty is void.
UPDATE: SOLVED
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
XDA mark said:
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
Click to expand...
Click to collapse
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
tallman43 said:
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
Click to expand...
Click to collapse
I can enter download mode normally, so I can use Odin to flash stuff.
I just flashed that kernel I wanted to flash before my phone went trippin, but after flash the same continues. Re-downloading ARHD 40 via my laptop now and going to reflash it via odin, hope that my phone can then let go of it's obsession of trying to get into recovery.
There must be a way to fix this, I didn't make a Titanium Backup for a while. Don't want to lose stuff just because I got some super rare weird problem... again. Why does tech hate me
EDIT:
Realized that I can't flash ARHD 40 because it only comes in zip not tar... anyway, tried flashing the newest version of philz touch recovery, still didn't change anything.
EDIT 2:
Flashed TWRP recovery via ODIN, now everything is fine again. It rebooted into TWRP normally, then choose to reboot the device. Everything is still there, like nothing ever happened.
THANK you lord!
Out of interest, how do you find the HTC 1 compared to the S3?
gsw5700 said:
Out of interest, how do you find the HTC 1 compared to the S3?
Click to expand...
Click to collapse
It's an entirely different phone, especially how it feels and looks. After using the One for such a long time, I find it super weird to hold a S3.. it feels so light and "cheap", though ergonomically the S3 is a tad easier to hold then the One. Overall I enjoy using the HTC One much more as it feels really solid.
Besides that it's fast and stable, what you would expect, but not much faster then a S3 with a good ROM. Screen is really excellent, this is also a big difference from the S3. It's a different type of screen and you can really notice. The speakers are the nicest you can get on a phone and compared to the S3 they are really a league above. The camera is average, sometimes it's great sometimes it isn't. Battery life is comparable to the S3.
Not that I didn't enjoy my S2 and S3 at the time, but I'm not really interested in the Galaxy line anymore at the moment. Samsung really has to do something amazing to get my attention again Will see what HTC brings with the successor of the HTC One, might upgrade to that one. I'm also curious about the iPhone 6 to be honest, the small screen is the main reason I haven't owned an iPhone in my life, if that changes I might want to try it. Or I might just use my current device for a second year for a change, since it's excellent
Many thanks for that, I now intend to take a look at the new HTC m8 - hoping the camera is better!
Me too. If they make a big leap with the camera and bring it on par with the iPhone 5S for example, it would be fantastic. Battery life should also be brought to the new higher standards of the LG G2.
If these 2 things happen they already got me, since it's a near perfect phone. Add some bonuses like making the bezels smaller/screen larger in the same body... don't think I could resist
So this morning I woke up and looked over at my phone as I usually do and the HTC white boot screen was showing. I decided to let it boot up thinking that overnight something happened. About 5 minutes later I went back and it was still at the boot screen. I decided to pull it from the charger and do a battery pull as I would usually do whenever something happens to this phone. After doing said battery pull... Nothing happened. I tried starting the phone up from essentially every single possible source I could think of. My laptop installed the drivers, but that was all that happened. I tried swapping batteries, but nothing happened either. This phone is a little over 2 years old so it may be the end of its life cycle, but I want to revive it just so I can back up everything onto my computer. I do have my media backed up to 3 different cloud sources, but it's better to have it on an actual folder rather than sorting through lord knows how many photos and putting them in separate folders. I am due for a new phone, but since I am 17, I do not have to ability to buy it off Swappa or any place so reviving the phone would be great. As of right now, the phone is still dead and may possibly be an aluminum brick.
NOTE: This phone is completely stock running on ICS 4.0.3 on Sense 3.6. I have done nothing with this phone in terms of flashing or rooting.
Your best chance would be to root it and flash a recovery and backup your data through the recovery, then you can try some fixes like flashing a rom or a RUU or just do a factory reset and see.. If you do a factory rest now you'll loose all your data
Sent from my HTC One using XDA Premium 4 mobile app
OK, guys, I'm talking about, most likely, a fairly unique problem I have with my Hisense Sero 7 Pro. So, considering the events of this have occurred over a year ago, pardon me if I have a bad memory. Get ready for story time!
Somehow, I could not get my Hisense Sero 7 Pro to boot up Cyanogenmod. I believe that is the software I loaded on it. For whatever reason, I could not boot it. I mean, fine whatever, right? I still have fastboot or bootloader and those combinations of buttons so that I reflash my software if needbe. It should technically be only a temp brick. But for whatever reason, it became really low on battery, perhaps from me unsuccessfully attempting to change it. I mean so low, that it reached that magical number where all of a sudden the tablet itself doesn't think it has a battery. And thus, it wouldn't even charge. I used a myriad of chargers and attempted all sorts of things to jump start it to a point where I could get it charging again, but it couldn't. Thus, I gave up on this tablet, and got a Nexus 7 2013.
Sometime later (ie, now), I fished this old tablet out of a shoe box when cleaning stuff out. I mean, not that old, but whatever. I thought, why not give it another go? I grabbed a random charger and plugged it in. I left it for 30 minutes to sit there, not doing anything. When I returned, to my surprise, it had reached the magical HISENSE boot screen it had been stuck at previously. This meant, that for some odd reason, my tablet had begun charging to some point, right? Alas, I was very excited. Yes, the tablet was still stuck at the HISENSE screen, flashing off and on again every minute or so, as if it's trying to boot a software that's essentially bricked, it's not there. But it has the electricity throbbing through its veins. And thus, that is enough for me to be excited. Just recently, I tried to boot into fastboot, I believe. And the device threw my a Low Battery symbol. The same kind it threw me when I tried to start it up way back when, and continued to attempt to, whilst it didn't charge, until it was deader than Abraham Lincoln.
But now I have the charger that will charge it, and that's good enough for me. Next Steps? Obviously, wait around, right? Perhaps it's below that 10% locked threshold needed for it to boot into fastboot or recovery? And if that's the case, I'll update you guys on that, but if that's the case, then great. I've got it at that screen.
Now what?
What do I do to flash Cyanogenmod, or Clockwork if I don't have it for whatever reason, and then Cyanogenmod and get this old thing working again? It's a project, true, but if I can get it functioning, this tablet would be awesome to have around the house, and, either way, it's a fun thing to work on.
Thanks for reading my story, and if you can help, great stuff!
i would suggest you install the latest lollipop.
first you will need to install a new recovery (neither the stock recover nor CWM will work with the newer roms)
http://forum.xda-developers.com/android/development/rom-sero-7-pro-uk-au-aosp-5-0-2r1-dopa5-t3015014
the above link has all the info, and files you need.
Issues after rooting Alcatel 5065N
Went into as much detail as I possibly could
n00b made a b00b00
After I discovered Androids had the ability to access everything in the operating system by adding a standard Linux function, rooting it, it undoubtedly peaked my interest. As I went through various Androids, I'd read up on ways to customize the phones via rooting or other methods.. but was always hesitant on actually rooting the device and risk having to tell my mom I broke my phone, ha.
Now, (somewhat of) an adult, I decided to finally root an Alcatel Tru 5065n, *silent woo.* Eager and full of impatience, I did some research and ended up using KingoRoot, supposedly the only functioning way to root my specific device, and rooted it through my PC. After playing with my phone for a while, I noticed a few issues with it's performance.. Whicchhhhh led me to panic over the likelihood of causing severe damage to my device. To Google!
I decided I wanted to un-root the system entirely. First un-rooted it within KingoRoot itself, still laggy, KingoRoot was still present in device although all the apps were gone, but root permission was no longer available. I wanted to rid my phone of KingoRoot completely, but couldn't find a way to do so without using another root service name "SuperSu." Which required, of course, re-rooting and installing KingoRoot and it's apps. My phone turned off during root, and took way longer than usual to reboot but KingoRoot said it had completed rooting while the device was mid-boot. Once the phone turned on, it had the apps re-installed and root was back in action. Now to rid my poor Alcatel of all things root.
Luckily, I managed to find @evildog1's thread "Replace KingoRoot with SuperSU manually without Terminal." I followed the instructions word for word, educated myself on whatever I didn't know, and successfully had a working SuperSu. I thought maybe, "Hey, this could make my phone run smoothly and I can just keep it rooted " Still lagging and freezing here and there, I refrained from using SuperSu's Full Unroot option.
As the days pass, an abundance of cuss words have been added to my vocabulary more and more & I find myself restarting the device more than actually using it. Apps would freeze. The keyboard crashes, pops-up for a split second to type A BLOODY WORD and the refuses to resurface unless restarted. Everything lags, but sometimes if I'm lucky an app won't glitch out and send me to the Open Apps Tab, which allows me to close all open tabs but then stays showing me the little broom. SMS notifications vanish into thin air. My home screen won't show any apps and then the device just literally will not do a damn thing but force restart. Oh, and then it takes FORFFRIGGINEVER to turn back on because "Android is Optimizing Apps." Since it was doing nothing tempt me to throw my phone into my pool, I tried using SuperSu's fancy Full Unroot every raves about.
It stayed at "Uninstalling, please wait ..." for over an hour. I gave up at that point and just switched to my iPod since I don't go out much and it's just been sitting on my counter for days.
Now, when it's on, it restarts on it's own, but gets stuck on the MetroPCS screen until the batteries die unless I take the batteries out myself and turn on the phone for it to only stay on for an hour or two until it decides to continue taunting me. I am now the un-proud owner of a paperweight.
Please help. All I want is to un-root my phone and restore my phone to it's original state before I ruined everything.
The best way to go back to original state is re-flash firmware (which will wipe your user data).
If you don't have firmware, contact your manufacturer and tell them about your issues (Don't mention "root")
Contact page: http://www.alcatel-mobile.com/global-en/company/contactus
I'm afraid it will cost you money, I hope it's free
I had this similar problem on my tablet after using Kingroot for 3 months and switching to Kingoroot caused even more issues. Instead factory reset, I contacted my manufacturer if they wanted to send me firmware. They gave me instruction and files to flash. I did flash, then root with Kingoroot and switch to SuperSU. My tablet still working perfectly with no issues so far.