Had oxygen mod installed and franco kernel etc and after months of using it fine I thought the phone was running a bit funny so thought it reinstall fresh.
I knew the files were still on my sd card so i went to go into bootloader or recovery and i got a black screen that had a message Firmware Update Step 1/2 Unpacking.
It finished and appears to put me back on Android 2.21
I then rooted the phone and tried installing clockword mod etc but was having all sorts of problems getting marketplace to work. Can search for apps but when i click install nothing happens. I did enter my gmail account details for sync and it can list my apps available from my account.
USB is not working, it shows up sometimes in the top bar but when i click connect nothing happens and the phone freezes or reboots.
I cant get into the bootloader screen it instead brings up the standard Android bootloader and wont recognise my rom on the sdcard.
I tried rooting with superoneclick and although it roots the phone it seems to cause the issues???
Is Superoneclick the only way of rooting U8800?
I want to start out stating that i am very familiar with android's but have never experienced anything like this.
The first thing I tried was to oem unlock it from fastboot, which it claimed to do however i am skeptical as nothing else seems to stick, attempted to install cwm and TWRP neither with any success, even though it says the action was performed successfully.
The strangest thing is that i deleted all the apps on the device from settings/app, but when i rebooted my device they all came back!
All i wanted to do was do a factory reset, which also claims to finish successfully but after rebooting from recovery mode, i am back where i started.
App Updates also do not work as every time the tablet reboots, the apps have to be re-updated.
Its like the tablet is stuck in a read only state and when it reboots all changes are lost.
Like i said, this thing is acting weird and i have no idea where to go from here. Any help would be greatly appreciated!
[Update: Tried RSDLite, same results, Result is PASS however after system reboot everything is the same.]
Another update, tried downloading HWI69 which is the stock rom, tried to fastboot each image but nothing sticks even though it seems to say it writes it to the system. I'm starting to think the NAND memory is locked up and cannot be written to anymore if that's even a possibility.
BUMP
Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.
Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-
So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.
I tried several methods before.
First was flashing the modem to work with GSM cards on calls and messages, but no data. I tried getting the MSL somehow but that didn't work. I flashed next TWRP without knowing anything about wiping the cache after installing SuperSU. I had to download the stock firmware again, and it was working stable until it shut down again when I flashed the new modem. I'm not sure what's causing the problem.
Keep in mind that I have two J3 Emerges, the one I'm modding and another one that has a cracked screen which functions very well. And I don't wanna mod the second J3 because of reasons.
EDIT: I just found out that formatting data via TWRP just causes the phone to behave normally, until somehow its connected to something... USB wasnt connected, and I think it has to be because of the phone checking the status of itself, despite being 'custom'.
EDIT 2: Found out, that the phone goes on a boot loop whenever I connect to the internet. Obviously, something must be going on.
EDIT 3: Looks like configuring the network was the issue... DANG. Anyone know of a way to bypass this bootloop?
Hello everyone, I have lots of issues with this tablet since I bought it. It works painfully slow, yet resetting it doesn't change anything, still the same problem. I also tried to root it via Kingroot and it werk, however it took me lot of time due to the system being unresponsive / unstable and almost useless. It comes with android 4.0.3 and I also tried looking up for any possibilites to reinstall the firmware since I'm extremely sure it could be caused from the firmware it also got installed from the factory. I also tried searching for custom roms and other ways around for TWRP or any custom recovery, but no result. I also tried up with the Flashify app to try extracting / backing up / dumping the recovery and the kernel but the app freezes up. I also tried a possibility to update the firmware from their official page, hence it failed to do so since it gives an error in their flashing software that dosen't tell me nor it logs it what it could be caused up from the connecting part.
primux.es/producto/tablets/tablet-primux-siroco-2-101/189
(not sure if anyone understands spanish thought but I can translate if needed)
This is the page from where I tried to download and install their software and their firmware down below on the page. primuxcomputers.es/primux/siroco2upgrade.pdf
There are the instructions where I tried to follow but at the "Imagen 9: Icono" part got me stuck in there. It requests me to insert the cable in the tablet holding the "Home" button and while holding it, plugging in the USB cable throught PC, and tap quickly the "Power" button 3 times. However it gives me a red X icon and yet nothing shows up in the devices: No ID, no other kind of detection no logs no nothing. After it showed up the X on the status, it disconnects itself and it changes to ready / green icon and plugs itself in again but nothing really happens to detect it again thought.
I also tried to boot in recovery mode but nothing happens menawhile Flashify keeps on the rebooting in recovery mode in loop doing nothing else... I'm seriously in pain with this tablet. And if you ask me to return it, not gonna even bother doing that..
I seriously hope any answer very soon and don't get dissapointed by the ignorance of this topic..