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.
Related
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
Hello
I have just recently obtained an HTC Desire HD from my brother, to start off with the hardware has been well taken care of, he is always careful, it was always in an otter case, and ran perfectly scratch free when I got it, so I already know there is nothing wrong with the hardware.
I was trying to root the device, I was using these instructions;
"how to permanently root Telus HTC Desire HD" (was going to be link but I can't yet)
The problem being that he had kept it well updated so I had to change the method a bit. I had to use the tacoroot method, it worked well, I was able to obtain "#" in the ADB, and modify my Misc_version. I then had trouble getting a hold of the PD98IMG.zip, I finally found one in the DHD_Downgrade_package.zip from "Downgrading and Rooting Your HTC Desire HD" (again would have been link) .
I then went to flash it, I had trouble because I didn't know you had to make a new goldcard every 2 uses or so, so that took a while, but when I realized that this morning I got to it, I flashed it, it let me and then that's where it all went down hill, or rather stopped.
It was flashing fine, as far as I saw it only needed to flash the radio. I was in the middle of making my lunch for work so I wasn't watching in intently.
When I looked back at it after a minute or so (and I had checked it in between, it was going fine) it was suddenly a blank screen, and I knew it was supposed to ask if I want to restart, I left it for a minute to nothing. then I decided to try force it to reboot, nothing.
Where I'm at now is that I've realized if I leave it with the battery in it for about five minutes or so it does turn on, only gets as far as the htc logo, and vibrates for probably 60 seconds. If its plugged into my computer, when its done vibrating my computer recognizes it (it dings and if I go under manage for my computer, its under devices) but that's it. Cant get into hboot as far as I've been able to try, though I haven't held the buttons for the entire five minutes, and ADB doesn't recognize it.
Please someone help, I am fairly newbish with android, I do have a tablet with android, but its from china so it barley counts lol.
Thanks a lot
-DonutFUN
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?
Hi guys,
I'm stuck with my LG G5 (H850) not booting after replacing the display. I bought the phone in used condition quite a while ago, and at some point the display cracked and the touchscreen did (and does) almost not work since it is hyper-sensitive now. I figured it stays somewhat usable after putting the phone into the freezer for 2-3 minutes. (apparently heat makes it worse).
So the thing now is, I bought a new phone at some point, but thought the LG still deserves a fix since i liked it for many reasons. I bought a pretty cheap display replacement (didn't want to invest too much money anymore). It was explicitly offered for H850. After replacing it, the phone wouldn't boot anymore. I just saw the LG splash coming and going in a 5s bootloop.
So I thought "maybe a hardware replacement requires to unlock the bootloader..." I unlocked the bootloader with the official guide (which was not easy as it required me to use the old crappy display to allow OEM unlock in android) and installed TWRP at the same time, cuz i thought it could prove helpful for other potential modifications.
After switching to the new display again, the phone would boot either OS and TWRP perfectly. The new display was also looking good. In the boot process it started showing "your device can not be checked for corruption", but that seems to be normal.
I thought "nice job" and put it down for a few weeks. Trying to start the phone again yesterday, I ran into the same issue again, bootloop. After performing a hard reset, which should bring you to TWRP, it's just the bootloop again. Going back to the old display: Booting fine but hardly usable. New display: Booting fine! Waiting for one night: No chance.
I think that's pretty weird. It's not that it doesn't work at all. I'm not an expert (which is why I'm asking you), but it seems the bootloader blocks booting with the new diplay, but only after having it switched off for a while. Once the phone has started, everything is fine.
What adds up to this story is that the phone wasn't perfectly fine beforehand. The old display (before cracking) provoked regular reboots and sometimes "your device is corrupted" would show up in that case. The reboots were gone - at least in a two days test i performed after getting the new display work.
On the other hand, there is something wrong with the basic capabilities of the bootloader with the new display: Fastboot mode works fine, but download mode only appears for a moment before rebooting.
Do you see any solution to this story? Anything I'm missing? I just grew up in a tradition of repairing things, but if you say that's a waste of time, I'm almost at the point of giving up
Thanks!
oliver t said:
tl;dr
Click to expand...
Click to collapse
Its not your new display, more likely motherboard fault.
Peace
I have a Verizon Ellipsis 7 tablet that is stuck in a boot loop. When I turn it on, I get the "Powered by Android" screen and then the screen goes blank but lit, and never gets to the next stage. I tried entering Factory Mode and cleared the eMMC, but after doing that I can't even get back into Factory Mode. (I spoke to a Verizon rep and he said clearing the eMMC likely cleared too much, and it now lacks the proper kernels to start up.)
I believe this whole fiasco may have started when I used the wrong charger after having not turned on the tablet for months. I stupidly ignored the warning, and the problems started soon after (although it worked perfectly normally for about a day first). I now have the correct charger and have fully charged the device overnight, but nothing's changed.
I think the only hope at this point is to reinstall the OS (the Verizon guy said "flash" it, but I'm not 100% sure what this involves). Can anyone help me do this, simply and safely? I'd like the original OS if possible, but otherwise I'm open to open-source alternatives. Thanks!
i just had this happen too -- and now i am stuck too;
however mine gets stuck at the verizon loading logo
Dude I'm right there with you. I'm almost at the point of installing Ubuntu touch lol I'm still not done with this fight though shoot I'll learn a whole new skill if need be damn things made me forfeit more than enough times.
hola busco firmware qmv7a