Database Info

HELP! Want to revive nexus half dead nexus one!

First of all this is my first attempt at rooting/reviving a Google phone. Although I have 10 +years of building computers etc. under my belt and I have owned multiple android devices since G1 launch so this should not be to hard to understand.
With that said. Here is my situation and as much knowledge as I have on how it arrived at the current state.
A friend of mine bought this Nexus on craigslist. It worked for a week or so, then would not boot up past boot screen icon (no lock on boot screen). I took it off his hands for $50.
Now I am able to get the phone in to the fastboot screen (when plugged in it reads 'fastboot usb'). I was also able to get into the the factory data reset screen. No matter the option I selected or cleared out it always returns me to the same frozen boot up image.
I downloaded SDK, superboot, drivers are installed (and updated ) and I have followed to the T all forum post on how to unlock the bootloader.
Everything goes great until... I get to this hiccup!! I am able to connect the device to and get a response with device pin number in command screen.
Then I type in 'fastboot oem unlock' and it gives me this terrific message:
... INFO[ERR] partition_read: :Failed to read page 261120 or it is em
INFOpty
INFO[DISPLAY_ERR] sp_custom partition: sp_custom_img_hd read err
INFOor!
INFO[DISPLAY_ERR] Can not load custom splash!
INFOLoading custom splash failed!
OKAY
What next????
I have also noticed that i get an interesting message when I first select bootloader on device, just for a second then returns to normal (pictures attached of this!)
One step I am unable to do that I believe may be the problem, since I have never been able to get past bootscreen on the device I have not been able to select the USB DEBUGGING option. Is there anyway around this?
If anyone is able to walk me through getting past this point and running vanilla 2.1 (I can take it from there ) I will donate $25 to this site as well as paypal you personally $25.. or you can have the entire $50 donated to the site
Thanks in advance for reading this post and helping a fellow Android lover!

Fix your Phone
I do not know if you will be able to fix it yourself but if you want you can contact google, send it in to them, and they will probably replace the phone for you. Assuming it has the standard 1 year warranty, you would be elligible for repairs and possibly google completely replacing your phone, giving you a new one. My G1 had problems and i tried fixing it myself with all kinds of stuff but eventually i contacted google and after i mailed it in they send me a new unit.

New Verizon Ellipsis 10 Tablet

I purchased the new Verizon Ellipsis 10 in late November. I believe the tablet was released for sale in mid November. My question is can it be rooted? I see the Ellipsis 7 and 8 can rooted. Wondering if anyone would be working on this or because it from Verizon no one cares. I can't find the tablet mentioned on any search that I do. I Have been checking daily to see if the device will have development on it. Thanks in advance for any information.

In the same boat. Need some help you smart tech guys out there. How can I root my Ellipsis 10?

I have the same tablet, and I do not think it could be rooted, at least not in the near future. The tablet comes encrypted (which I am not too happy about....I just noticed it) and cannot be decrypted, even if you do a factory reset. It runs fine as it is, but would be greatly enhanced if it could be decrypted. I also think there are very few devs on this forum that really care a lot about this tablet, so you may not see too much work being done on it.

Same here, just picked one up. Really hoping that there will be a root for this at some point soon. Someone please help us all out!

wish I would have saved the 50$ now, and got the Samsung tablet for free... it's OK, the biggest problem for me is the audio output being too quiet. all the "volume booster's" on the play store have been jenky, to say the least. if anyone has suggestions of a "good, volume booster", or work around, please let me know. thank you for you time.

Oh, No! Sadness!
mikekoz said:
I have the same tablet, and I do not think it could be rooted, at least not in the near future. The tablet comes encrypted (which I am not too happy about....I just noticed it) and cannot be decrypted, even if you do a factory reset. It runs fine as it is, but would be greatly enhanced if it could be decrypted. I also think there are very few devs on this forum that really care a lot about this tablet, so you may not see too much work being done on it.
Click to expand...
Click to collapse
Please, influence some senior devs to help you with this issue!

qtair7 firmware files
https: / / " www dropbox com " /s/f8ye7yw24mjqiva/IR7-20C59.7z?dl=0
just fix the text when u enter in address bar (-""'s,+.'s)

so i downloaded the IR7-20C59..7z package from the software upgrade/repair tool from verizon... I extracted the files and sent the boot.img to my tablet (qtair7) and used magisk manager to patch the boot.img then I used ubuntu to adb pull the magisk-patched-boot.img and modded it using abootimg and changed a few things from default.prop.. ro.secure=0 ro.debuggable=1 and drm.service.enabled=false .. (just saying im an amateur android enthusiast with little experience. ive played with image kitchens and compiled a kernel and ported a rom for the samsung on5 indie variant to have sound on my smg550t1. worked but all google services and apps crash constantly.. but anyways) i dont really know what im doing just saying this is what i did. repacked magisk-patched-boot-new.img then i sent the adb reboot fastboot command to my tablet and it fastboot flashing unlock , fastboot flashing unlock boot, fastboot flash boot magisk-patched-boot-new.img. fastboot continue, fastboot reboot.. the tablet boots and is rooted with magisk.. now i installed busybox to sbin. i have done this 2 times. im not sure if its the busybox or the magisk, but when i reboot following the above steps i get the verizon splash screen and in the bottom righthand corner of the screen it says modified. then boots to recovery. and now can only boot to recovery. now i have the upgrade/repair tool .iso on usb flashdrive that i use to repair my device from this state. which sometimes is a pita.. i have to continually attempt to repair sometimes it takes 2 days.. before it finally works.. i dont know why.. but it boots from fastboot the first time fine. and would like to know how to stop the soft bricking of my device or how i can obtain a twrp.img for this device QTAIR7.. please help ive been working on rooting my tablet for over a year. and feel that i am very close . thanx

Anyone interested in the system.img or any other partitions.. the Dropbox file is only the recovery flash files. I think. I know I couldn't edit system.img from the file with any kitchen but the system.img I dd'd from my device can be edited with kitchen. It's is 3.7gb so in not going to post unless someone can do something with them

Please share some info on the file you posted,..
jonthn41 said:
qtair7 firmware files
https: / / " www dropbox com " /s/f8ye7yw24mjqiva/IR7-20C59.7z?dl=0
just fix the text when u enter in address bar (-""'s,+.'s)
Click to expand...
Click to collapse
Hello, THANK YOU!! This is the most progress I have made in months! I don't know what it is, what it offers, or what to do with it yet, but it is a step!
Could you maybe say what it is, what it will do (how it helps..) and what to do with it?
My Verizon Ellipsis 10 (qtair7), even after wiping the cache, even after doing a factory reset, (even after 'disabling' all but FEW APPS!) JUST SPONTANEOUSLY REBOOTS every time i try to do anything, I try to watch a video it is fine for 5 minutes or an hour then I push volume up or touch the screen and suddenly it reboots, totally random, Clearing the cache gets it to works for a while but it always does it again it has NEVER been usable really,.. It pops up some screen often like"Google Play Services have stopped' something like that,.. Will this help with any of that? Make it more,. stable?
I wish I could just do ANYThING simple to make it better I just use it for video playback,.
THANK YOU!

I have the same tab with the same issues. Rebooting, random cut out and full on reboot. Just before it became target practice I decided to take it apart, just because that's what I do when I'm bored and my ADHD is taking over. I looked up the tab on youtube to see if there was any vids of how to get it apart and found a guy that said he fixed the with the tablet that no one could figure out. Meh I was like ok I'll give him a couple seconds checked it out. He found that all connections, screws holding boards down, and power were all loose. Once he went through all of that it had fixed the issues. So I tried it and damn, everything from screws holding boards down to power feeds were all loose, really bad loose. Got mine working good now. Haven't had issues since. Now if I can get it rooted I'll be good. And I suspect the loose connections would also potentially cause the battery to go bad from excessive amperage draw and charge in short time, over time.

Swiss Mobility Zur805 can it be saved?

Hey smarter people than me,
I have a Swiss Mobility ZUR805 tablet that worked great until about a year ago when it started having boot problems, something in the realm of "CANNOT FIND SHELL" (which to my understanding means no operating system found??).
After a year of sitting in a drawer, and me deciding I would try an salvage it as a nanny cam, kids movie tab, or whatever, I decided to read some threads and become my own hero. So, I either messed up, tangled myself up more, or this thing is a brick. Please help me decide or point me in the right direction. This is what I know.
-I found no support on this tab, but there is lots of help on the same problem. This is just to say that generic solutions (resetting BIOS and playing around with the boot options) did not work.
-I have access to BIOS and some other options by pressing ESC on boot, but there is not much I would know to do after that.
-After playing around with boot options, It stopped getting the shell error message and started going straight to "ENTERING DNX MODE, WAITING FOR FASTBOOT COMMAND", wait 2 mins, reboot and repeat
-Trying the POWER + VOL (and different combinations) to enter recovery mode does nothing
-I cannot find the original software (is it called a ROM?) to tray and restore through sd card
-I have read that I cannot install any version of Android, it needs to be specific to this tab. Is this true? How can I get a working version?
-Is this just as a pc, meaning hardware + operating system + drivers = working device?
-The INTEL logo is the only thing that will appear other than the error message. Does this mean I can install Windows or Ubuntu?
-Should I?
-What would I need?
Thanks for any and all help.

Swiss Mobility Zur805 can it be saved?

Hey smarter people than me,
I have a Swiss Mobility ZUR805 tablet that worked great until about a year ago when it started having boot problems, something in the realm of "CANNOT FIND SHELL" (which to my understanding means no operating system found??).
After a year of sitting in a drawer, and me deciding I would try an salvage it as a nanny cam, kids movie tab, or whatever, I decided to read some threads and become my own hero. So, I either messed up, tangled myself up more, or this thing is a brick. Please help me decide or point me in the right direction. This is what I know.
-I found no support on this tab, but there is lots of help on the same problem. This is just to say that generic solutions (resetting BIOS and playing around with the boot options) did not work.
-I have access to BIOS and some other options by pressing ESC on boot, but there is not much I would know to do after that.
-After playing around with boot options, It stopped getting the shell error message and started going straight to "ENTERING DNX MODE, WAITING FOR FASTBOOT COMMAND", wait 2 mins, reboot and repeat
-Trying the POWER + VOL (and different combinations) to enter recovery mode does nothing
-I cannot find the original software (is it called a ROM?) to tray and restore through sd card
-I have read that I cannot install any version of Android, it needs to be specific to this tab. Is this true? How can I get a working version?
-Is this just as a pc, meaning hardware + operating system + drivers = working device?
-The INTEL logo is the only thing that will appear other than the error message. Does this mean I can install Windows or Ubuntu?
-Should I?
-What would I need?
Thanks for any and all help.

Recover files from bootlooping Zenfone6

Dear all,
from the occasional reboot my Zenfone performed every now in a while (which didn't bother me too much) it now reboots so fast that it usually has not yet booted to the point where I could get data off the device before it reboots again.
As always, the backup is too old and I want to extract some data off the device. Most important are a few KBs worth of text notes. Here come some questions:
- It seems to be a hardware fault. Are there educated guesses what may give me a few last moments with the device to extract data? Heat? Freezing?
- Are there professional data recovery companies dealing with smartphones such that they can extract data from the chips without the phone working?
- As it is a Qualcomm device: Would any access via QDLoader work or would it be as unstable as the rest of the phone?
I appreciate any input. And yes, I know that I didn't backup often enough.
Thanks,
weaker

which rom are you on?

Sorry for the late reply.
I'm on stock ROM with Magisk. In the end when it became worse, I let Magisk restore the images but this definitely seems to be hardware-related. I also did no overclocking and I don't use games on the phone so I think that it is also not a thermal issue.
To keep the interested ones updated how it evolved: The situation is now as follows:
I tried to boot into recovery via fastbooting the TWRP (the one I used many times successfully for my phone) after one of the phone bootings was stable for enough seconds so have ADB contact and go to fastboot mode. I hoped to be able to interact more stabily in the recovery. However, the result was that the phone rebooted (I am unsure if the TWRP transfer was finished before that) and then the charging screen appeared and the charging screen remained constantly on, even when pulling the cable. It didn't react to any keypresses in that state.
I let it drain the battery (which was only a few hours as the screen was always on). Then, I plugged the phone in and it booted normally and was stable for 15 minutes or so, which gave me enough time to save the most important data. Phew.
This session however seemed to be the last farewell. The phone started to bootloop and I switched it off*. Now the phone has always a black off screen and doesn't respond to anything: Pressing (and holding) the power button, also in combination with Vol+ or Vol-. Also plugging a cable to charge doesn't create any reaction.
* switching it off worked the following way: The unlocked bootloader shows that one could press the power button to pause the boot. I can't think of why this might be a useful function in a normal situation. However, in my situation I could pause the boot and after some time it would switch off. That way I could at least break the bootloop.

you will have to boot into qloader to be able to recover your phone...
follow step by step exactly what is mentioned in the below link, ypu should be able to recover your phone :
Here’s how to unbrick Asus ZenFone 6 (Asus 6z) from QDLOADER 9008 mode - PiunikaWeb
Is your Asus ZenFone 6 (Asus 6z) hard-bricked? You can use still flash via QDLOADER 9008 mode to give a new life to your dead handset.
piunikaweb.com

Sorry to be the prick here, but next time post this in Q&A section. This one is for posting development (Kernels and ROMs)

OK, no offense taken. I thought that I would need to resort to some TWRP magic to get data off my device.
@MOD: Feel free to move thread where it fits best.

For the sake of completeness:
The phone is back from RMA. According to the sparse documentation they exchanged the mainboard and battery and some connector. Some firmwares are now newer than on the old mainboard (little surprise here). Bootloader unlock worked also on the new phone (some report that this would not work by default after an RMA, for me it did).
So, ASUS did a great job dealing with the issue.