I purchased a used (and poorly) Blackjelly BJ689 7" tablet with phone support which had been rooted and severely screwed up. I spent a couple of days hunting for this tablet without any luck, and the phone numbers for sales and service are dead.
The original ROM supported the phone, and the Phone worked to a degree, and the GPS signal level meter appeared in the upper toolbar. After some searching, i ended up installing the UBEROID ROM from techknow (option 120) I tried about 20 different versions, most supporting the phone, but once installed, i couldnt see ANY link whatsoever to access the phone, or turn it on. The Uberoud ROM software said it had backed up the original ROM, which it did, but later trying to re-install it freezes the tablet.
Could someone throw me a lifeline and try and either identify the device further so i can track down the original ROM, or tell me why the Uberoid ROM versions dont show me the phone option.
Thanking you in advance,
John
Related
Hi guys. Love this site but I am encountering some issues! I am having problems with the drivers (it appears), of my p990h. I am new to android (only had my device a week), and have duly thrown myself in the deep end to try and make the most from the device and have encountered some issues. I am in Colombia and bought the phone here. I ‘rooted’ the device using the ‘Super One Click’ method and had no issues. I then performed the fatory reset and installed the ‘Cm9.0.0-rco-p990-unofficial’ rom (build [email protected]). I didn’t experience issues up to this point. However (and i know i messed up here), i then flashed baseband version 1035.21_20110725 using smartflash. Big mistake as then the time on the phone changed all to European time, and now although the device can be read by my computer, it cannot connect to it and a yellow exclamation appears on the device in device manager. I have tried everyway to update this, but no joy. Tried reflashing with smartflash, but now nothing happens when the phone is connected (nothing appears in the ‘coms port’ box). If i use the lg tool, it doesn’t even list my p990 as a device whose drivers i can download.
So basically I would like to know if anyone can help me:
a) get the drivers working properly again so I can connect the device and update.
And
b) if anyone can get me the 1035.21_20110602 baseband files to go back to how it was previously. Have looked everywhere but no luck. I downloaded one, but i cant seem to find a way to use use it (it appears as a clockworkmod folder and macosx folder. I haven’t used them as i couldn’t figure out how!
May i need to re-root my device, could this be the issue? This had occurred to me that the superuser settings may have something to do with this.
I also want to be able to restore my phone to its stock settings as i really need my camera back up and going properly whilst here in Colombia.
I have spent the last week trawling these forums reading everyone’s posts and learning from you guys, so a big thanks out there to you all who have got me this far – many thanks. Seems like a great community and im looking forward to getting more involved, and learning about the murky waters of android (even though im having some difficulties i love it!) . I apologise for any poor wording and general noobiness that may cause any misunderstanding! I will try and answer any questions/replies i may get as accurately as possible.
I really hope someone can help me as I cant keep going in circles – i have a 12 hour bus ride tomorrow so gotta get it done.
Many thanks in you lovely people!
try flash a new rom CM7
The 4.0.4 OTA update was waiting for me when I woke up this morning. I started the install but when it went to reboot it hung up with a picture of the Android man on his back with a red error/warning triangle.
I haven't done anything with it, hoping someone might be able to help me out.
The phone is rooted but running 4.0.2 stock rom. the battery was a little low when i started the install, but i plugged it in before starting.
Thanks in advance for help,
jvoosh
the reason is that your phone is rooted ,so ... if you want OTA ,you had better unroot you rom or ruu
so can I hard reset the phone (pull the battery) without screwing anything up and then figure out how to unroot the phone?
thanks for your help,
j
Ditto
I'm in exactly the same boat, and hope someone answers this before I try a battery pull.
EDIT: I read around and found some people describing our situation, and mentioning that they did battery pulls to no avail. So I did, and nothing broke. However, the update didn't go through, and now I'm trying to figure out why this happened.
Same issue
I'm having the same issue. Phone got the IMM76k update, and after downloaded, was prompted to restart and install. So i did, gets through part of the install, and then goes to the android man on his back with a red exclamation mark. Have tried multiple times, all to no avail. Now, when I click check for update, it says system up to date, but still on 4.0.2.
Non-rooted, bootloader unlocked...anyone have any luck fixing this?
After downloading update, get Android man on back with red exclamation point
I'm having some difficulty getting the update to install, along the lines of some of the comments posted before mine:
I was able to force download the OTA update (IMM76K) according to the instructions on this original post. (It took a few tries, but eventually worked.)
I select the "Restart & Install" option (which is the only option available to me), and it restarts.
I get the relatively familiar Android man with his blue-green glowing polyhedron wireframe guts spinning, and a progress bar beneath him. After getting through what looks like about 20%, it slows down significantly, and I get the Android man on his back with a red exclamation point above him where the polyhedron used to be. I don't recall seeing any specific error message any of the three times that I tried this. (The first time, I did a battery pull; the second and third times, I just waited, and it eventually restarted on its own.) Needless to say, I'm still on 4.0.2.
I'm afraid I'm not very familiar with different version names and so forth (e.g,. I don't know what yakju is), but this was a phone that Verizon sent me in December 2011 here in the US.
Here's the information from my "About phone" page:
Model number: Galaxy Nexus
Android version: 4.0.2
Baseband version: I515.09 V.EK05 / I515.EK02
Kernel version: 3.0.8-gaaa2611 [email protected] #1
Build number: ICL53F
When I first got the phone, I immediately unlocked the bootloader and rooted it. I did NOT install a custom recovery, nor did I install any custom ROM.
It sounds like there might be some kind of validation error, but I do not recall doing anything that would make my OS non-stock, except perhaps side-loading Google Wallet, but since that doesn't even require root, I can't imagine that it would have any effect. My Superuser app shows only the following apps to have ever used root permissions: BusyBox Free, Secure Settings, Superuser, Terminal Emulator, and Titanium Backup. I've only used BusyBox and Secure Settings with Tasker to automate certain tasks, but nothing crazy! Mostly, I just need root for Titanium Backup. (I cannot recall exactly what I restored from my stock Gingerbread Droid X, but I was very careful to only restore apps and their corresponding app data--and I avoided restoring any Google-provided apps.) Even my tethering is done through an app not requiring root (SVTP).
Any advice (not requiring that I do a factory reset or flash a custom recovery or ROM) would be greatly appreciated! I'd also like to hear about people who have similar circumstances, but didn't have problems updating (so that I can rule out various factors).
Thank you in advance!
same exact issue here.
A "solution", albeit less than ideal
The OTA update eventually came to my phone naturally, and it still didn't work. (No surprise there.)
I called up Verizon tech support, and they had me do the Google Services Framework workaround to try to force the update again. Of course, it didn't work.
They said "We're going to need you to reset your device." (i.e., to factory default).
I told them that was wholly unacceptable, since I want to make sure that all my settings are preserved. (I'm kind of obsessive compulsive about things being set the way I like them, and Titanium Backup, as great a program as it is, has sometimes caused some trouble for me when restoring system settings, and especially since I'd be doing a restore after upgrading the OS, I was nervous about that option.)
Verizon got Samsung on the phone. They had no advice except "We're going to need you to reset your device." Both the Verizon rep and I told him that wasn't acceptable.
So Verizon's "solution" was to send me a new device, allow me five days to get everything transferred over, and then have me return the old device.
Up side: In case there was something wrong with my hardware or something else got messed up, I get a new device that I can get set up with the exact same settings as the old one.
Down side: The "new device" is refurbished, so there could potentially be some kind of baggage.
The "new device" came with 4.0.2. I booted it up without the SIM card, skipped all the logging in to Google, and immediately started going through the steps to unlock the bootloader and root the device. (I used the Galaxy Nexus Root Toolkit, which worked like a charm on a 64-bit Windows 7 machine I had lying around.) After unlocking and rooting, I logged into the device with my Google credentials and let it restore my settings and apps that I had downloaded from Google Play.
Then, it notified me that the 4.0.4 (IMM76K) update was available, so I installed that, and it worked without a problem.
Then, I installed the SIM card and got the new device activated through Verizon's website for activation.
Then, with both devices side by side, I went through every phone setting and made sure it's what I wanted, I made sure every app was installed (and if it was a non-Google Play app, I restored it through Titanium Backup), and I restored data for apps that don't store their data in the cloud (e.g., various games) through Titanium Backup. (I made a backup of my old device with Titanium Backup and transferred it over to the new device after getting the new one up and running.)
Everything seems to be working just fine, and the "new device" runs a bit faster and smoother than the old device, and that's with both devices rebooting and then going through the exact same "click paths", side by side.
So it's a bit of a hassle, but everyone who has a Galaxy Nexus should still be under warranty, so if you're polite with your Verizon tech support representative, they may be willing to help you out.
Verizon can sometimes be infuriating with their update release schedule and keeping their customers informed, but they sure do a good job accommodating their customers in other ways.
I realize this isn't really a "solution" to the Android man on his back problem, but this seemed to be the path of least resistance for me, and I'm pretty happy with the outcome so far. (It's been less than 24 hours since I got the "new device" set up!)
Other things I realized I should have tried (and still may, before I wipe my phone and send it back):
- uninstalling BusyBox (through the app itself, since it makes modifications to the system) and Secure Settings
- unrooting
Good luck!
My friend who has a nexus has his bootloader unlocked and CWM on it. He got the OTA today on his way into work and like you guys, he has a broken android when he boots up. We can get into CMW but we are unable to mount his internal SD storage onto our computer and he has no ROM zips on his phone. Any advice as to how to get his phone up and running?
Will wiping the system/data fix it? Is there a way to get a ROM like AOKP onto the device outside of CWM?
Edit: After several reboots it decided to just boot into the stock ROM. Really strange. Anyhow, flashed AOKP and all is well now.
Hey guys!
First off, i was searching through loads of forums and attempted different solutions. Anything to get it back working. This only made it worse
What happened was as follows:
After having CM 10.1 or some version of it (had the OS at 4.3 i believe), my phone was very slow, so slow in fact that i got so mad at it that i almost bit through it. So one day when i was in a tent at the foot of a mountain all alone (not that long ago) i decided to rollback the phone to its original state from backup i made some months ago before i upgraded the OS. At the same time just before this i backed up the current build just in case. Using ClockWorkMod 3pointsomething.
It went through everything and then asked me: Do you want to root this device? (or something in those lines). I, having no clue, clicked one of the million "no" on the screen.
After this it rebooted with errors saying "Can't detect this drive can't detect that drive". In other words, it couldn't detect niether Internal SD nor External SD. While having the Samsung logo being displayed without booting if i didn't go into "Volume Up, Menu Key and Start your tiny engines!".
I thought i could fix it and looked through tremendous amount of internets in attempt to fix it. Neither Odin nor Heimdall Frontend could detect the device even after installing the drivers and samsung kies and messing about with those two in between.
After a while i ended up with "Phone . . ! in a orange triangle . . PC" aka black screen of death, while the phone can go into download mode. Which in my hand is equally useless as no program can detect it still.
Now i just decided to start a new thread even though there is endless amount of other threads but none seem to cover exactly this as i haven't yet managed to fix it. Plus a response on progress is always pleasant as i personally don't know when i succeed unless phone works fully again.
How bad off am i?
Any input will be greatly appreciated! :victory:
Hoping not to have to spend money on a new one and as far as i've gathered this can be solved - Anybody can give me some tips on where to look or what i could try?
Adventurove said:
Hoping not to have to spend money on a new one and as far as i've gathered this can be solved - Anybody can give me some tips on where to look or what i could try?
Click to expand...
Click to collapse
First you are posting in the wrong location as i9000 has its own forum here for Q&A and others too
second click on My Android Solutions (link below) and try methods to fix USB connection problems first after that get into download mode and use a rescue kit from MY Android Collections (link below) or follow this to flash a Gingerbread JVU stock ROM
Check this out! You , YES! you are an " Android ". Not your phone but U.
TL;DR - Flashed a ROM designed for N3+ (which is supposed to be same phone) but touch screen is unresponsive now. Need help with SP MDT or editing uboot
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?).
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
____________________________________________________________________________________________
Hello everyone, like title says I have unresponsive touchscreen on my Star N9800 phone. It's pretty much a new phone, octa core, quad core GPU, 2GB RAM, 16GB storage, etc.
What I've done is I flashed the ROM designed for Star N3+ (which is supposed to be same phone) but my touch screen is unresponsive ever since then. I've googled and read some articles on xda about SP MDT. It's a tool which can help us choose the display driver we want the phone to run with. I actually ran into a problem when i downloaded SP MDT. I can select the database etc, but when i get to scatter file it just doesn't want to load it. Either it's incorrect name or file type. I've downloaded 3 original ROMs from needrom.com and strangely the scatters seem to be different. But none is accepted by SP MDT. I need someone of knowledge who can teach me where to find uboot and how to edit it correctly. I'm not a linux/android programmer and I really don't wanna get involved into much programming. I understand basic stuff, i can find files on the system, i can edit build prop correctly, remove or edit boot_logo, boot anim etc, but this is a bit more than that. 2
Please share some knowledge with me and please don't point me to google. There's no solution there, i've googled for 3 days now. The last resort for me is to make a post here (and hopefully don't get ignored for spamming because this isn't spam).
My email is: [email protected] - you can notify me here if I don't get automatically emailed by xda.
Thanks in advance.
BUMP
Have no solution but would like to learn as well if anyone can help us...
I had the same issue but gave up and flashed another rom instead.
Flashing another ROM didn't help my problem. Well partially it did. I've flashed 2014-1-7 original N9800 ROM and the touchscreen only needs 1 or 2 off/ons till it starts working. I'm kinda fine with it because it was completely unusable. Flashing drivers with SP MDT didn't really help. I've tried flashing RX5720TM_828A (from N3+ ROMs) and LP057APK (default in N9800 ROMs) and RX5720TM_813A (2nd in N9800 ROMs), and so far my touchscreen works only with 813A LCM driver. When i turn off the phone and then hold VOL- & POWER & OFF/ON it goes to factory mode. There i clicked version and it showed that 813A is installed as LCM driver, BUT touchscreen says (null). Could it be that my digitizer is no longer connected or what? Cuz it sometimes works correctly without turning the display off/on at all.
EDIT 15. July, 2014.
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?). It is possible that digitizer is detected but not working?
Even if i boot into recovery, screen doesn't react to touches.
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
Apparently it's the calibration which ****ed up my phone. I'm now trying to figure out how to calibrate the screen through CWM.
ever find a solution?
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.
Touch screen sometimes not react
AlexZap said:
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.
Click to expand...
Click to collapse
-------------------------------------------------------
I have exactly the same issue and same signes, the phone itself is working good, ring for incomming phone but the the screen is not reacting i cannot take the call, it receives emails.
Did someone have a solution please let me know... thanks
My phone is star N9800, 2Gb memory and 16 Gb storage, android 4.4.2 originaly installed and was working fine during 9 months
Touchscreen - hardware failure
Hi,
I am wondering if you may have experience and be able to help me with my Star N9008 phone which has has had its touch screen stop working while I had it in storage for about 3 months.
Very well stored, no shock, no humidity. I keep it with my laptop backpack as a spare in case my everyday phone fails.
Today I powered it up to make sure battery was good (found it good at 95%) and update applications, etc. Basically, just checking it was still good to serve as a backup should I need it.
Thing is, I found the touch screen is completely unresponsive. Connected a mouse to it and verified all was working good, did up the updates, etc.. using the mouse. Reboot and boot into service mode and restore menu. Also, no touchscreen response (I use TWRP). Thus, it must be hardware failure.
From experience, would you know what would cause this, and how to resolve?
Thank you.
So, its been a while.
So, it's been a while. I still have the phone in storage and pity it doesn't work...
I haven't bothered opening up the phone if I don't know what to really try and also risk damaging it.
Also didn't bother ordering a new digitizer to replace as it's economically unviable.... the phone is now really getting behind as new tech is further evolving, so I do unfortunately see it going in the rubbish soon (along with two brand new batteries I had purchased for it just before it died).
Has anyone been successful at finding the culprit?
In my case, it was fine and very well stored... so I don't really have an explanation other than the phone possibly having a 'countdown timer' to break it... (yeah, a bit too conspiratorial, lol)
I did not find a solution yet , phone still sits in storage
Folks,
During a recent power outage my battery completely drained for the first time. Powering on after a full charge, started getting screen msgs (yellow text) info on some system internals. tried rebooting, and got "failure to load efs". and the phone comes back up in Factory test mode. I had never attempted any modification on this phone and everything looked stock to me. I had bought used from B&H, so cannot swear to its complete history. Samsung recommended a "smart Recovery from Best Buy that after two swap-outs i am still getting all the above msg's. I have no experience in rooting or anything else, but have a background in software. Info found through searches seems to indicate Verizon Samsung sg3's may be the most difficult to add mods. I found a stock rom, and loaded it successfully via odin. Best Buy guy said he loaded an original stock as well, and still no luck. Even though this happened after a hardware issue, and i know its firmware, at a loss as to what is causing this. it generally degrades performance of the phone in everything, including linking to playstore to download apps. I have everything backed up, with nothing to lose if anyone has a path to a working phone....I'm game. running 4.4.2