Database Develop

OTA update did this to me..

Carrier: Telkomsel
Country / Language: Indonesia / English
OS / Browser / build number (if applicable): 2.1 / .... / ERD79
Could be because of overheating, mine totally not working anymore :
1. Vibrate
2. Microphone
3. Misplaced button : Home > Back and Back > Home. (when I pressed back, it goes to home and the other way).
4. MicroSD slot
5. SIM card reads very low signal
All of these because the OTA update I received and installed.. It was ok at the beginning and then it starting to acting up, at first : hang occasionally, have to take out battery and rebooted, but then it gets worse: won't boot at all.. sometimes it just stuck on the boot logo, have to take out battery again.... and the other day it just doesn't boot, I even tried to go to bootloader / recovery, but the phone just doesn't seem to respond.
I thought could be the battery, so I charge overnight and in the morning it was hot (not warm).. but able to boot to bootloader only.
After a lot of reading and possible cause, I made decision to revert back before the OTA update (ERE27), so I downloaded all the necessary files from http://forum.xda-developers.com/showthread.php?t=614850, and successfully went back to the original state (I even downgrade the radio to the oldest/default one (ERD79)).
And SUCCESS!! my N1 boot normally and I did all the usual settings, including the wifi and network.. then it started to update again... *sigh. And I'm back to square one again.. so I did everything again.. and now I disable network and wifi, because I am affraid if it found a internet connection it will download the OTA update again and will update.
Unfortunately, to do all that I unlocked the bootloader, therefore void my warranty.. I didn't care as long as I got my N1 working again.. but after all the works I did, it's pretty much useless now.
It seems that all the problem is at the bottom part of N1..
Anybody else have this problem? or am I the unlucky one..
I tried to using CM files, but since the SD doesn't get recognise I could not..

You're saying that even after reverting to ERE27, your SD card isn't accessible from Recovery? Your problem is very odd... but flashing to another ROM should solve the problem of the OTA updates redownloading everything.

You're saying that even after reverting to ERE27 > I went back from ERE27 to ERD79.
I can only flashing .img from fastboot, that is the only access I can get to my N1..
I cannot go to recovery using amon-ra, i flashed the recovery ok, but everytime I put into recovery it just loads the X boot logo and does nothing else, but when i connect usb, it ask for a qualcomm cdma driver, I don't know what kind of driver that is and I don't see my N1 doing anything.
so I cannot load another rom, because I only know that cooked rom are stored in the SD card, and my N1 cannot read microSD card.
here is some video I took : sorry, low quality http://www.youtube.com/watch?v=Bv7P5lz9bVY

[Q] Stuck on Welcome Screen... lenovo k3 note

(its my dad phone)
hi so yestarday i installed the "aosp-k3note-5.1.0" rom and it all went fine but worked slow and without bluetooth.
so today when i got home my dad told me he just installed a new rom from romnation(he dosent remember which rom but he said it was an offical rom)
BUT he downloaded it stright to the phone and installed it without erasing anything(date/cache/davlik)...
so when he tried to use the phone it will gives errors like gaps stoped working and all kind of stuff that made the phone useless...
so i downloaded "VIBEUI_V2.8_1526_7.80.1_DEV_K50-T5" rom and gapps64 and went to the CMW and this time i erased the date cach and davlik and installed the rom and after that the gapps
and now i cant get past the welcome screnn becuase as soon as i choose english or chinse it will give me "wlan has stopped" and return to the language menu...
so now im stuck becuase i cant use adb to root it and SP tools dosent work too(i tried to keep it pluged for an hour and it still wont do anything with ot without the battery)
what can i do? and thanks for any help...

Try this to get CWM back on.
rollcage0 said:
(its my dad phone)
hi so yestarday i installed the "aosp-k3note-5.1.0" rom and it all went fine but worked slow and without bluetooth.
so today when i got home my dad told me he just installed a new rom from romnation(he dosent remember which rom but he said it was an offical rom)
BUT he downloaded it stright to the phone and installed it without erasing anything(date/cache/davlik)...
so when he tried to use the phone it will gives errors like gaps stoped working and all kind of stuff that made the phone useless...
so i downloaded "VIBEUI_V2.8_1526_7.80.1_DEV_K50-T5" rom and gapps64 and went to the CMW and this time i erased the date cach and davlik and installed the rom and after that the gapps
and now i cant get past the welcome screnn becuase as soon as i choose english or chinse it will give me "wlan has stopped" and return to the language menu...
so now im stuck becuase i cant use adb to root it and SP tools dosent work too(i tried to keep it pluged for an hour and it still wont do anything with ot without the battery)
what can i do? and thanks for any help...
Click to expand...
Click to collapse
Try removing the battery and plugging the phone in to the PC.
Start SP Tools with CWM set in the scatter and only recovery ticked
Press Download in SP tools and then insert the battery
CWM should download to phone
If that fails repeat but plug the phone in once you press Download, then insert the battery.

rollcage0 said:
(its my dad phone)
hi so yestarday i installed the "aosp-k3note-5.1.0" rom and it all went fine but worked slow and without bluetooth.
so today when i got home my dad told me he just installed a new rom from romnation(he dosent remember which rom but he said it was an offical rom)
BUT he downloaded it stright to the phone and installed it without erasing anything(date/cache/davlik)...
so when he tried to use the phone it will gives errors like gaps stoped working and all kind of stuff that made the phone useless...
so i downloaded "VIBEUI_V2.8_1526_7.80.1_DEV_K50-T5" rom and gapps64 and went to the CMW and this time i erased the date cach and davlik and installed the rom and after that the gapps
and now i cant get past the welcome screnn becuase as soon as i choose english or chinse it will give me "wlan has stopped" and return to the language menu...
so now im stuck becuase i cant use adb to root it and SP tools dosent work too(i tried to keep it pluged for an hour and it still wont do anything with ot without the battery)
what can i do? and thanks for any help...
Click to expand...
Click to collapse
Omg..i have almost exactly the same problem and the solution that MrAAnderson suggested didn't work.Here's how i ended in this problem.I was running VIBEUI_V3.0_1602_7.407.1_DEV_K50-T5 ROM on TWRP recovery made By Pr1nc3V app Lenovo K3 Note Manager [v2.1].Since i had annoying bug with "R" (roaming icon) and "gapps stopped working" issue i wanted to re-flash same ROM.I entered into TWRP recowery,cleared dalvik+cache,rebooted into recovery again.Now i wanted to flash ROM,but it didn't flash it gave me an error,same thing happens if i try to flash stock recovery (i even tried naming ROM and recovery as "recovery.zip" and "update.zip").Rebooted the phone but i'm also stucked on welcome screen where i can't pass it because of "Unfortunately,WLAN stopped working".
Tried to flash ROM and stock recovery with SPFlashTool but the tool doesn't see phone at all,same as Lenovo K3 Note Manager by Pr1nc3V .Right now i'm running out of solutions for this mess i created,any advice will help.Help me please to restore my phone.
EDIT: i just realized that i actually made a "factory reset" in TWRP recovery..not just wipe data,cache and dalvik.....what are my options now folks?

Ok i'm happy to announce that i resolved my problem (after a panic mode on,lol).Here is what i did..
1. Obviously you have to get back on your stock (original,ugly chinese-english one) recovery (in case you already didn't..).To do that i used SP Flash tool.(i wouldn't go into details but if you need just ask).
After that we have following situation..stock recovery + dev ROM (which isn't working well).
2.If you try to flash any ROM in this state it will fail (based on my experience,i tried to flash exactly same ROM which is already installed..no way.).So now next step is to get a CUSTOM (TWRP or CM) recovery,again flashing it with SP Flash tools.
From this point you can choose wher would you go...STOCK rom ,MODDED one ...anything actually.I hope i clarified a bit.

sptools is not detecting my device

please help a person who doesn't know much about ROMs, kernels, root and so on.

i'm in desperate need for guide please,
so i first off i had some questions (excuse my stupidity but i really couldn't find any answers around)
1) can an never-rooted android device's build number change or is it always the same? like with stock/official updates only?
2) my recovery mode (stock/system recovery) aborts every single installation file (official rom from the Asus website) without even opening the package, it's like i press 'install update from sd card' then as i press the zip file, it immediately says 'installation aborted' without even typing any other significations/steps, and the same happened for the kernals zip files too. so does that mean my recovery mode is corrupted or something is wrong with it?
3) i noticed some slight changes in my recovery since the last bootloop i had and had to use it back then, for example the dead android screen appearing after choosing the recovery mode, at first it used to say 'no command' under the dead android, but this time it doesn't say anything, just the dead android image only until i press power button and volume up to get the recovery options. so does that mean my firmware version changes since last time or my recovery is corrupted or it just means nothing?
4) is there aNYWAY to know my build number of a phone in bootloop (not rooted but bootloader unlocked)
so my initial problem is; i had my asus zenfone go zc500tg on march 2016. it was working so fine actually (using it like a default user not actually knowing anything about roms/flashing/recovery etc) until july of 2017 when i noticed my phone was a bit slow (out of the ordinary) and it used to get SO hot while using it normally and battery drained pretty faster than before, but i didn't know what to do tbh so i just kind of ignored something was off. but not long after these symptoms, the booting of my phone got slower and slower, until it reached its max by staying more than three hours just doing the 'optimizing apps' on the booting screen until it booted, so i thought it was a virus that would go away after a factory reset, and after the reset, it got worse, until it stopped booting and got into a bootloop. I panicked then because i didn't have the slightest idea what was happening until some internet searching guided me into the world of bootloops and custom roms and recovery. so i eventually managed to fix the bootloop and it worked fine for several months until it started to lag again and boot slowly and got the second bootloop, and that i fixed like the first one by installing the rom from the asus website then putting it on the sd card sand flashing it through recovery,
the third bootloop was quite the same, except that i did something additional in recovery mode, i pressed "backup user data" and that did a nandroid backup then i restored it smoothly after flashing the rom.
the fourth bootloop was a bit different, i as always downloaded the same firmware as the times before and flashed it and backed up user data too, but the odd thing that happened was me getting a message box that won't go away that said "unfortunately, the process com.android.phone has stopped" the phone worked but the sim cards weren't recognized and the message box was coming and going every second, so i noticed that the message box went away (nearly) when i got my sd card out, but still the phone app and the sim cards were corrupted,i thought the issue was from my sd card at first but i eventually, (coincidentally tbh) managed to fix it by doing the OTA update that was due, (that bootloop was fixed on the date of January 13th 2018)
then my phone was working so fine and everything was alright.
then shortly after (january 20th 2018) i was on whatsapp normally then suddenly ALL the things on my phone came crashing in front of me : TONS of endless message boxes saying things like "unfortunately, the process com.(any app on my phone) has stopped"
that i literally panicked and tears welled up in my eyes, so i rebooted the phone and while rebooting it did a (relatively quick) "optimizing apps" but as it booted everything was the dreaded same, all the apps crashing, then with the second rebooting was the current bootloop. i thought it was the same as before and just downloaded the usual zip file i use everytime but while flashing it (it did the same as mentioned in question 2 above) but it aborted instantly so i went and downloaded every rom there but it was the same so i went and tried the kernal zips too but always the same (i can't read my build number through the system recovery because it is like not fitting well in the screen si half the number isn't there that's why i asked question number 4)
so can anyone help me please? i'm in desperate need for help, i'm literally crying while typing this because i can't afford another phone and i'm so scared.

also is there a way to install custom recovery to not rooted device while in bootloop?
or if the system recovery was actually corrupted what do i do? :crying:

Data Partition always destroyed after turning off phone

Hello there.
I have a Huawei P9 (EVA-L09) with an unlocked bootloader and a custom ROM.
Since a few days I started experiencing something completely weird.
Every time I happen to turn off my phone (often only because the phone had gotten quite warm and I want it to cool down then) I then land in the boot animation and get stuck there. After forcefully rebooting the phone from there (about half of an hour) I held the Volume Up key for three seconds during the warning screen and eRecovery told me about the Data Partition to be badly damaged and it would be recommended to recover it.
There are two ways I can do from here (and also did):
First way is to let it recover using eRecovery, connect to my wireless connection, however the phone always tells me that there was a problem getting the package info for my phone. (Does Huawei stopped supporting the P9 eventually?)
The second way is to run TWRP and reinstall the custom ROM (In my case RROS 5.8.5 for my P9) and to never turn my phone off again. However this isn't always possible to keep it on since it also could happen that I'm not at home and my battery suddenly died.
Installing the stock ROM (or a custom ROM based on a stock ROM) however doesn't work. The stock ROM itself simply won't get installed, neither over the dload method or TWRP or fastboot and a custom ROM based on the stock ROM results in having my phone simply getting a black screen when locking it and then I need to reboot it to use it again.
What can I do? Could it be that my flash memory could be corrupted or something could have happened with one of the partitions of the phone?
Greetings.
EDIT: I managed to install a stock firmware using this link right here.
After the stock firmware was installed, doing a factory reset and wiping the cache every problem I mentioned above this edit vanished.

Install custom/stock rom with locked bootloader and no access to OS

Hi there,
I got a bricked G5S+, which I reported in another thread already.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
That happened after I rebootet the cellphone for a longer time.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me and now cannot access android anymore to do so.
Anyway I thought: fine: I will just flash the stock OS again taking care of the software defect.
After having had some issues I flashed Sanders (SANDERS_NPS26.116-26_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) following that thread here:
https://animetrick.com/flash-stock-rom-moto-g5s-plus-locked-bootloader-2018/
It is quite similar as this thread, which deals with installing a stock OS to a bootloader-locked phone:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
The thing is I followed all steps but still get the same error:
A lying down android with a red questionmark and saying 'no command'.
Does anyone have an idea what else to try?
I am not aversed to install a custom Rom, such as the official RR v6.0.0, but I have no idea how to do so with a currently bricked phone.
Maybe you guys have a solution for me to unbrick and finally use my phone again.
Thanks a lot!
Regards from Germany
Matt

Hey bro Im not sure if you still need help but, if so can you try to boot into a recovery?

Hi Carlos,
yes I still need help.
I can boot into recovery. And fastboot runs and detects the phone, too.
Any idea what I can do?

Go ahead and download twrp from the Roms sections and also begin the process to unlock the boot loader, we can see if it still can be done without having enabled the setting in the developer sections, and if so we can either then flash the recovery and a custom rom or install stock again.
Sent from my iDevice running Smoothshake v11.3.1

I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
There is no need anymore to install a custom rom (at least not currently )
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!

I have fallen into same issue, i cannot install any custom rom or recovery to it but i can access fastboot & one recovery that has update via adb sideload / sd card but nothing works, shows failed line 2 error / install aborted .
the device just showing oem locked in fastboot & rom install or recovery install fails & says cause too many links
the phone starts & stucks after the motorola logo
anybody with any idea?