[Q] Bluetooth doesn't turn on - Galaxy S 5 Q&A, Help & Troubleshooting

Hey guys,
I searched the web already but I can't find a solution. My S5 won't turn bluetooth on anymore. It's rooted but after rootprocess, BT worked fine. I can't remember that I've done something around BT. I've deleted Data and Cache already and rebooted the phone afterwards but still no Bluetooth. I opened Quick Connect and a Toast appeared which said "Bluetooth activated" but there wasn't the logo in the status bar and the icon in the notification center was also grey. Hope that you can help me.
Pozdrav
Croatia1

Any solutions?

Hey mate..
Any solution yet..?
Mine wont turn on still.
Galaxy S5 LTE

Reinstall ROM
Maybe the cause of the problem is that you downloaded an invalid root and it did something to the bluetooth. I highly recommend reflashing a stock rom. See if anything changes. Thank you :victory:

la2o said:
Maybe the cause of the problem is that you downloaded an invalid root and it did something to the bluetooth. I highly recommend reflashing a stock rom. See if anything changes. Thank you :victory:
Click to expand...
Click to collapse
This can't be the reason, becausw after I rooted it, BT worked fine.
Pozdrav
Croatia1

Yes.. Mine worked for a while as well and then it dsnt now....
I have the stock rom.
Galaxy S5 LTE

For the gentleman with the stock rom - you can try rebooting into service mode (holding home+volume up and then pressing power) and wipe your cache there - and then try to switch on bluetooth. If that does not work - warranty claim.
As for the rooted phone - you cannot be sure how stable the implementation of bluetooth drivers etc on that rom is. It could have worked at first and later - due to any number of reasons - could stop. I'd really suggest flashing a stock rom and checking - that way you'll be sure the hardware is ok. If not ok - warranty claim.

rnrnrn said:
For the gentleman with the stock rom - you can try rebooting into service mode (holding home+volume up and then pressing power) and wipe your cache there - and then try to switch on bluetooth. If that does not work - warranty claim.
As for the rooted phone - you cannot be sure how stable the implementation of bluetooth drivers etc on that rom is. It could have worked at first and later - due to any number of reasons - could stop. I'd really suggest flashing a stock rom and checking - that way you'll be sure the hardware is ok. If not ok - warranty claim.
Click to expand...
Click to collapse
First, thanks for the tip, sadly it didn't work.
Second, I'm already on Stock Samsung Rom, it's only rooted, I didn't even flashed a custom recovery.
Pozdrav
Croatia1

Hold on, I remember that I've done something around BusyBox with the app from Steven Stericson. Could Busybox brake my bluetooth?

croatia1 said:
Hold on, I remember that I've done something around BusyBox with the app from Steven Stericson. Could Busybox brake my bluetooth?
Click to expand...
Click to collapse
Yes, it could although that wouldn't be a normal result. But yes, it's possible. Depends on what you did with the Busybox configuration.
.

fffft said:
Yes, it could although that wouldn't be a normal result. But yes, it's possible. Depends on what you did with the Busybox configuration.
.
Click to expand...
Click to collapse
Just installed the 1.22.1 version of Busybox with the pro app that's all. Maybe it killed some symlinks.

Well if you practice safe mods.. you'll have made a backup before installing Busybox. So temporarily restore your backup and see if the issue resolves?
If you don't make backups, then you have a lot more work as you have to look for a pattern and /or guess at the cause.
.

I usually always make Nandroid Backups but in this case not. I'm afraid that Busybox will kill my S5 if I deinstall it. What if I flash a Stock Custom rom via CWM? Of course with a full wipe

I doubt Busybox is the cause, but I cannot rule it out. Only because it was a recent change does it move up the suspect list.
Still way too many variables in my mind. I'd probably start by installing a 100% stock firmware temporarily, just for troubleshooting. Confirm that bluetooth works i.e. not a stock issue or hardware failure. Then install your core apps one by one.. see if you can narrow down the conflict fairly rapidly.
But that is hardly the only way to go about it. As you like.. you have to start somewhere and either cull a lot of possibilities or wait for a pattern to emerge. Search the forum too, just in case it's some issue affecting a larger number of people - which might offer more clues.
Good luck.
.

fffft said:
I doubt Busybox is the cause, but I cannot rule it out. Only because it was a recent change does it move up the suspect list.
Still way too many variables in my mind. I'd probably start by installing a 100% stock firmware temporarily, just for troubleshooting. Confirm that bluetooth works i.e. not a stock issue or hardware failure. Then install your core apps one by one.. see if you can narrow down the conflict fairly rapidly.
But that is hardly the only way to go about it. As you like.. you have to start somewhere and either cull a lot of possibilities or wait for a pattern to emerge. Search the forum too, just in case it's some issue affecting a larger number of people - which might offer more clues.
Good luck.
.
Click to expand...
Click to collapse
Thanks mate, I'll post if I have success.
Pozdrav
Croatia1

Good news!
Before I flashed a new firmware with Odin I decided to flash a Custom Rom. Flashed new bootloader + modem and performed a "Wipe for new Rom" in Philz CWM, flashed the rom, set up my apps and settings and, BT works again. Thanks for your help
Pozdrav
Croatia1

Great to hear that so it was just a bit of software acting up - good to know
Please do change the title of your thread to solved

Related

How to do a complete system restore?

Let me apologize for being a newbie as I come from 5 years of using Windows Mobile and just got my first Tab/Android 2 weeks ago. This is all new to me.
After messing up with some system files and factory applications (like I removed stk.apk and other things) I decided to do a full hardware reset. This is something I did many times in Windows Mobile... whats bad get overwriten in ROM and whats missing gets back where it was. But is seems on this Tab this is not the case.
After the full resetthings only got dramatically worse. All the missing system apps are still missing (I thought they be "restored") and nothing works, just crashes one after the next, cant use anything. I also tried with the system off the method of pressing and holding the “Volume Up” and “Power” buttons at the same time, then after recovery screen appears navigate and select “wipe data / Factory reset” and pressing the “Home” button, but after that and the system re-starts, same thing! All bad.
Can someone please explain to me how to do a full rstore where all system files, all and everythign gets back as it was in the Tab as it was shipped? What a flippin' nightmare... Windows Mobile, I love you!
Thanks in advance.
settings/privacy/factory reset.
natious said:
settings/privacy/factory reset.
Click to expand...
Click to collapse
No no, that doesnt restore anything! All missing files dont get restored. I need a full stock ROM image and restore EVERYTHING. Thats what I dont know where to get and how to do...
VeEuzUKY said:
No no, that doesnt restore anything! All missing files dont get restored. I need a full stock ROM image and restore EVERYTHING. Thats what I dont know where to get and how to do...
Click to expand...
Click to collapse
Yeh i realized that after reading your post properly sorry man, i guess you can just flash one of roms found here, like rotos or modaco's JMI, that would atlest give you a work tab till you can find a stock samsung rom
If you dont have cwm installed you can flash with odin or heidmill (sp)
natious said:
Yeh i realized that after reading your post properly sorry man, i guess you can just flash one of roms found here, like rotos or modaco's JMI, that would atlest give you a work tab till you can find a stock samsung rom
If you dont have cwm installed you can flash with odin or heidmill (sp)
Click to expand...
Click to collapse
Yeah, I enever flashed the Tab. Can U advise me on a stable "OK" ROM? Where can i find odin or heidmill and some sort of a guide to help me step-by-step? I have positively no clue what I am doing... sorry for my ignorance... I feel thoroughly stupid...
I got lucky and found this site. Hope yours is a Verizon Tab
I'm not allowed to post links. But go to google type in "galaxy tab system restore" and click on the "[How TO] Restore VZW Galaxy Tab to stock DJ11" link
It's in the droidforums. net
VeEuzUKY said:
Yeah, I enever flashed the Tab. Can U advise me on a stable "OK" ROM? Where can i find odin or heidmill and some sort of a guide to help me step-by-step? I have positively no clue what I am doing... sorry for my ignorance... I feel thoroughly stupid...
Click to expand...
Click to collapse
First of all, you need to post what "type" of Tab you have, which is generally going to be determined by your country and/or carrier.
Flashing a new Android ROM isn't a particularly complicated process, but it can seem daunting if you've not done it before - this is especially true when using Odin or Heimdall over a "recovery" based flash.
FWIW, the reason your "factory reset" didn't work is because all is essentially does it reformat the /data partition (a generalisation, but close enough for these purposes). On a stock Tab, you cannot mount /system as read/write, so you are unable to change the contents of that partition. This means that on a stock Tab, /system should never change.
However, when you root the device you give yourself the ability to remount /system as read/write and thus make changes which are not going to affected by a factory reset.
Take a look at this thread - lots of useful information there!
Regards,
Dave
foxmeister said:
First of all, you need to post what "type" of Tab you have, which is generally going to be determined by your country and/or carrier.
Flashing a new Android ROM isn't a particularly complicated process, but it can seem daunting if you've not done it before - this is especially true when using Odin or Heimdall over a "recovery" based flash.
FWIW, the reason your "factory reset" didn't work is because all is essentially does it reformat the /data partition (a generalisation, but close enough for these purposes). On a stock Tab, you cannot mount /system as read/write, so you are unable to change the contents of that partition. This means that on a stock Tab, /system should never change.
However, when you root the device you give yourself the ability to remount /system as read/write and thus make changes which are not going to affected by a factory reset.
Take a look at this thread - lots of useful information there!
Regards,
Dave
Click to expand...
Click to collapse
Thanks for the link... yes Ive seen that master thread... I just keep reading from link to link and thread to thread and all gets more complicated, I keep downloading more files and installing more stuff but in the end Im more confused and positively going no where. There is not one simple, from start to finish guideline on how to do the process of wiping all data and installing a new ROM. Ive done this endless times on many phones under WinMo, and with more or less difficulty never had any problems getting this done. But here, the more I read the more utterly chaotically confused I am.
I am yet to have anyone explain what type of Tab I have. Its GSM, I think its Euro, bought in Hong Kong. I have found out all bootloaders and stuff seem to be cleaer and I should be able to flash anything. Its a GT-P1000 and Baseband P1000ZHJJ1. This is all I know.
VeEuzUKY said:
Thanks for the link... yes Ive seen that master thread... I just keep reading from link to link and thread to thread and all gets more complicated, I keep downloading more files and installing more stuff but in the end Im more confused and positively going no where. There is not one simple, from start to finish guideline on how to do the process of wiping all data and installing a new ROM. Ive done this endless times on many phones under WinMo, and with more or less difficulty never had any problems getting this done. But here, the more I read the more utterly chaotically confused I am.
I am yet to have anyone explain what type of Tab I have. Its GSM, I think its Euro, bought in Hong Kong. I have found out all bootloaders and stuff seem to be cleaer and I should be able to flash anything. Its a GT-P1000 and Baseband P1000ZHJJ1. This is all I know.
Click to expand...
Click to collapse
Its pretty much the same as mine then, so i recommend you use modacos kernel and rom and installing cwm
cwm - http://forum.xda-developers.com/showthread.php?t=870690
Kernel - http://forum.xda-developers.com/showthread.php?t=925760
Rom - http://forum.xda-developers.com/showthread.php?t=941423
If you have and external sd card (one that you put into the side of the tab)
You can flash the ext4 kernel via odin, its pretty simple, there will be instructions in the threads.
Are you still able to go on the market? If so download the cwm app and use that so you get the awesome recovery menu and features, you can then use it to flash a new rom and make backups that are really really easy to restore. Seeing it looks like you like to mess around with stuff i suggest it the best way to go.
Hope this helps
Ok thanks for the tips. I have finally managed to get the Tab working again and flashed it with Roto JMI Pre-Rooted Firmware v2. All seems OK at this point. Ill check the links you sent me and follow-up. Flashing Roto JMI Pre-Rooted Firmware v2 with Odin3 1.7 is easy so I hope modacos kernel and rom and installing cwm are easy as well.
A little off topic:
I just got my SGT on Friday and want to root&/flash custom ROM. Gonna definitely root soon...But thinking of holding off on the custom ROM until CM7 is stable or a nice clean Honeycomb ROM is cooked
Does ClockWorkMod require root? I know Titanium Backup does. Can't really do any "fun" things with the tab until it's rooted it seems.

DHD in trouble-any ideas?

So,the DHD was running perfectly fine till yesterday,when something strange started happening.The damn thing wouldn't show some widgets(all were non-HTC widgets btw) and a message about the SD card popped up,but I couldn't see what it was saying,as the phone rebooted.After it booted the battery had dropped from about 90% to 10% btw.What was strange?Well,as soon as screen went off,it wouldn't turn on again.Pulled battery,rebooted.The same again and again and again.I thought it had to do with my UV settings.Removed my scripts,rebooted.Still the same.I also removed some ram-optimization scripts I was testing,in case that was the problem.Again,nothing changed,the problem persisted.Then I changed kernels(LordClockan's Sense kernel v4,LeeDroid's kernel v4,RCMix Team's v11 and v10) to no avail.I also changed roms(RCMix3D to LordClockan's 0.8 ICS build and back),but STILL nothing.I even changed recoveries(From CWM 4.0.0.2 to 4EXT Touch 1.0.2 RC1) but it didn't fix the problem,even after a full wipe-format of ALL partitions.I tried removing the SD card and the SIM card in case one of them was causing the problem,but the same happened.
Then I thought "****,let's see what the hell happens".To better explain what happens,when I try to turn the screen back on(Even if it was off for like 1sec) it doesn't turn on.The buttons' lights turn on,but nothing responds.However,I can hear background notifications and stuff.While it's working,it also doesn't reboot or power off when prompted to do so,either through some app or through the power menu.
So,back to what I was saying,I decided to run a logcat to see what happens.But adb won't recognize the device at all.No matter if it's "adb reboot" or "adb logcat" or anything,it says "device not found".
So,what I haven't tried yet is changing radios,but:
i)I'm afraid it may finish it off in case something goes even more wrong
ii)I don't think it's in any way related to the problem
So,before I quit trying and call HTC for warranty purposes(IF I can still flash an official RUU for Christ's sake),do you guys have any ideas?I'm out of ideas right now.AND it sounds hardware related or something(Although I can still transfer files from my PC to the SD card).
Thanks in advance guys.
my phone wouldn't turn back on after a phone call ended, and it turns out the proximity sensor was playing up, so i used the recalibrator from here: http://forum.xda-developers.com/showthread.php?t=951858
this probably won't be the right solution for you, because this isn't the typical problem that the recalibrator solves, your problem sounds very strange. but it might be worth a shot anyway.
you should be able to get in to bootloader to flash a stock rom. If adb and the power menu are both not working, boot in to recovery from inside the 4ext recovery control app or Rom Manager app, then in recovery go to the power menu and there's the option to boot in to bootloader. and since you can put things on the SD still, put a PD98IMG.zip on the sd and away you go.
if that doesn't fix it, it's probably hardware unfortunately
good luck!
maatsby said:
my phone wouldn't turn back on after a phone call ended, and it turns out the proximity sensor was playing up, so i used the recalibrator from here: http://forum.xda-developers.com/showthread.php?t=951858
this probably won't be the right solution for you, because this isn't the typical problem that the recalibrator solves, your problem sounds very strange. but it might be worth a shot anyway.
you should be able to get in to bootloader to flash a stock rom. If adb and the power menu are both not working, boot in to recovery from inside the 4ext recovery control app or Rom Manager app, then in recovery go to the power menu and there's the option to boot in to bootloader. and since you can put things on the SD still, put a PD98IMG.zip on the sd and away you go.
if that doesn't fix it, it's probably hardware unfortunately
good luck!
Click to expand...
Click to collapse
Well,I know my way around the device,but sadly that's not enough this time.
Do you by any chance know what stock rom I should flash?I kinda lost track of things since I bought my Galaxy S II...
Thanks for the reply too pal.
Adb kill-server
Adb start-server
Then try and do other adb commands, see if that works
Sent from my HTC Desire HD A9191 using xda premium
tolis626 said:
Well,I know my way around the device,but sadly that's not enough this time.
Do you by any chance know what stock rom I should flash?I kinda lost track of things since I bought my Galaxy S II...
Thanks for the reply too pal.
Click to expand...
Click to collapse
No worries. I returned to stock last week for warranty, I flashed this: http://www.multiupload.com/BTJ8KY0KH9
from this thread: http://forum.xda-developers.com/showthread.php?t=905003
I used this one because it is easily re-rooted with visionary. So if you flash the stock rom and the problem is fixed you can head back in to rooting land straight away. But unfortunately, if you have to send it to HTC after all, they'll probably OTA upgrade it before giving it back
maatsby said:
No worries. I returned to stock last week for warranty, I flashed this: http://www.multiupload.com/BTJ8KY0KH9
from this thread: http://forum.xda-developers.com/showthread.php?t=905003
I used this one because it is easily re-rooted with visionary. So if you flash the stock rom and the problem is fixed you can head back in to rooting land straight away. But unfortunately, if you have to send it to HTC after all, they'll probably OTA upgrade it before giving it back
Click to expand...
Click to collapse
Thank you dude.Will try and report back.I hope everything goes too well.Or,in that aspect,too wrong in case I can get a new device.
So,after a downgrade to stock 1.32.xx version(the one maatsby posted) it seems to be solved...Strange indeed,but I'm happy!I love this phone.
I'm gonna check whether rerooting will make the problem reappear.I certainly hope not.
Anyway,thanks for the help,especially you maatsby!
tolis626 said:
So,after a downgrade to stock 1.32.xx version(the one maatsby posted) it seems to be solved...Strange indeed,but I'm happy!I love this phone.
I'm gonna check whether rerooting will make the problem reappear.I certainly hope not.
Anyway,thanks for the help,especially you maatsby!
Click to expand...
Click to collapse
no worries mate, and thanks for the update. I'm glad that fixed it!
It would be interesting to know what went wrong!
maatsby said:
no worries mate, and thanks for the update. I'm glad that fixed it!
It would be interesting to know what went wrong!
Click to expand...
Click to collapse
Yes,it would be interesting,but I even nandroid-ed back to my previous ROM(the one the problems first appeared on) and it's working flawlessly.If it does it again I'll make sure to post it here in case others have the same problem in the future.

HELP Recovery doesn't load (is installed) & when it boots up a S.Screen-Loop appairs

HELP Recovery doesn't load (is installed) & when it boots up a S.Screen-Loop appairs
Hey
Wow, having a hard time now without my new galaxy s4.
Can't get access the recovery mode anymore and when it boots up, a screen of death appairs in a very strange way.
It seems that a script, can't load properly, because I deactivated something, that's why it allways resets itself after it's finished to display the loading samsung screen again. I can go into the system for 1-5 seconds only, then the loading screen appairs again - all the time.
I allready installed everything and it worked fine, with wanamlite rom and phil'z cwm.
But I did some security finetuning, removing (mostly freezing, but then uninstalling) lots of the bloat and spying system apps... thats why it happened. I know what I was doing, but not exactly (new apk's, new JB). Trial and Error. Allready got the results I wanted, but it wasn't finished and I messed up something.
This is fkn crazy about Android 4, coming from 2.3 - the new smartphones send ALL YOUR PRIVATE DATA EVERYWHERE (google,samsung and LOT's of other companies) in stock and even in all the roms, by default. Even Snapshots and Voice-Recordings in backround. Just go to the Options/Security/Certificated Authorities... or check the triggers with autostarts or just use a taskmanager.... 99,99% of the people aren't even aware of this.
However, I before I go crazy about all this I want to say, that I want to use the phone and all the priviledges and functions of course, but without all the spy****, that is also reducing my batterie like hell. It's not about, that the accu isn't strong enough, but it is used all the time by many different things
Ok now, what can I do ? I have a working cwm backup, but I can't access the recovery anymore!
I have access to the download mode.
I allready tried a different rom (this one) flashed with odin, after it finishes, it loads to recoveryAUTOmode, but after that, the same problem persists.
this one=this version:
Model: GT-I9505 (4.2.2)
PDA: XXUBMH1
PHONE: XXUBMH1
CSC: OXXBMH1 (29 codes) (NOTE: KIES will NOT recognize this FW due to CSC mismatch..)
Kernel: 3.4.0-1081224 (05.08)
Build Date: 05.08.2013
Changelist: 1081224
Click to expand...
Click to collapse
because I wanted to use the same version as wanamlite and I don't want 4.3 yet, because of app-compatibility and some more... it's just getting worse, (android 4.4 is reallly ****ed up with wlan-on all the time..rumors..)
My Question to the developers here is exactly does Recovery need to work properly ?? (systemfiles,apk's,scripts)
Why the Samsung-Screen-Bootloop appairs and what script triggers it ?
Tried with ADB-GUI - but it doesn't seem to connect - but testing is needed, didn't try everything yet
this tool: http://forum.xda-developers.com/showthread.php?t=2237530
You know, I don't have nothing to hide, but I want to have my privacy and freedom anyway - I just want to have a clean, secure Phone as possible and I disable and uninstall everything I don't need and will never use all the bloat ****, also I don't want to send ALL my data to google, samsung and all the other companys and CA's.
If I where a developer I would probably bring out a great,clean and secure rom for everyone, however that isn't wanted by google and the big companys and the nwo agenda.
However, it seem's that allmost no one (developers and users) cares about security and privacy at all.
You can only be secure, if you root your phone and modify alot of settings, triggers and remove lot's of apps (apk's) and use several apps to do so. It normally cost's you hours to get everything in place and more hours to figure out all this stuff... but a very advanced good script, could do all the modifications in seconds. Whatever, that **** is to big for me now, I will get over it... will you get over it ? I would like to join this big elite group, if I could, because they have everything (allmost. Also I don't want to sell my soul... what a dillema
Now seriously please - I really need some help by a pro
Hope you can help me.
I think there is a good solution, it lies in downloadmode and flashing the right thing or using adb the right way.
Ok that's it. thanks for reading.
I wish you a good day and all the best.
cya
ps: my signature is over 2 years old.
(•.•) said:
Hey
Wow, having a hard time now without my new galaxy s4.
Can't get access the recovery mode anymore and when it boots up, a screen of death appairs in a very strange way.
It seems that a script, can't load properly, because I deactivated something, that's why it allways resets itself after it's finished to display the loading samsung screen again. I can go into the system for 1-5 seconds only, then the loading screen appairs again - all the time.
I allready installed everything and it worked fine, with wanamlite rom and phil'z cwm.
But I did some security finetuning, removing (mostly freezing, but then uninstalling) lots of the bloat and spying system apps... thats why it happened. I know what I was doing, but not exactly (new apk's, new JB). Trial and Error. Allready got the results I wanted, but it wasn't finished and I messed up something.
This is fkn crazy about Android 4, coming from 2.3 - the new smartphones send ALL YOUR PRIVATE DATA EVERYWHERE (google,samsung and LOT's of other companies) in stock and even in all the roms, by default. Even Snapshots and Voice-Recordings in backround. Just go to the Options/Security/Certificated Authorities... or check the triggers with autostarts or just use a taskmanager.... 99,99% of the people aren't even aware of this.
However, I before I go crazy about all this I want to say, that I want to use the phone and all the priviledges and functions of course, but without all the spy****, that is also reducing my batterie like hell. It's not about, that the accu isn't strong enough, but it is used all the time by many different things
Ok now, what can I do ? I have a working cwm backup, but I can't access the recovery anymore!
I have access to the download mode.
I allready tried a different rom (this one) flashed with odin, after it finishes, it loads to recoveryAUTOmode, but after that, the same problem persists.
this one=this version:
because I wanted to use the same version as wanamlite and I don't want 4.3 yet, because of app-compatibility and some more... it's just getting worse, (android 4.4 is reallly ****ed up with wlan-on all the time..rumors..)
My Question to the developers here is exactly does Recovery need to work properly ?? (systemfiles,apk's,scripts)
Why the Samsung-Screen-Bootloop appairs and what script triggers it ?
Tried with ADB-GUI - but it doesn't seem to connect - but testing is needed, didn't try everything yet
this tool: http://forum.xda-developers.com/showthread.php?t=2237530
You know, I don't have nothing to hide, but I want to have my privacy and freedom anyway - I just want to have a clean, secure Phone as possible and I disable and uninstall everything I don't need and will never use all the bloat ****, also I don't want to send ALL my data to google, samsung and all the other companys and CA's.
If I where a developer I would probably bring out a great,clean and secure rom for everyone, however that isn't wanted by google and the big companys and the nwo agenda.
However, it seem's that allmost no one (developers and users) cares about security and privacy at all.
You can only be secure, if you root your phone and modify alot of settings, triggers and remove lot's of apps (apk's) and use several apps to do so. It normally cost's you hours to get everything in place and more hours to figure out all this stuff... but a very advanced good script, could do all the modifications in seconds. Whatever, that **** is to big for me now, I will get over it... will you get over it ? I would like to join this big elite group, if I could, because they have everything (allmost. Also I don't want to sell my soul... what a dillema
Now seriously please - I really need some help by a pro
Hope you can help me.
I think there is a good solution, it lies in downloadmode and flashing the right thing or using adb the right way.
Ok that's it. thanks for reading.
I wish you a good day and all the best.
cya
ps: my signature is over 2 years old.
Click to expand...
Click to collapse
Did you just smash your keyboard typing all this? I hope not.. because its quite irritating to see someone oosting such things on a updating guide. You can pm me if u want help. But since u asked here.
Here you go.
Download adonis.pit from my second post
Flash it in odin as pit.
Flash a stock 4.2.2 firmware package
Install whatever recovery you want.
And you are done.
You can go back to recovery.
Sent from my GT-I9500 using Tapatalk
Degrated Shadow said:
Did you just smash your keyboard typing all this? I hope not.. because its quite irritating to see someone oosting such things on a updating guide. You can pm me if u want help. But since u asked here.
Here you go.
Download adonis.pit from my second post
Flash it in odin as pit.
Flash a stock 4.2.2 firmware package
Install whatever recovery you want.
And you are done.
You can go back to recovery.
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
that sounds really useful. I will try it now. big thanks! However I have a 9505... is the pit really needed? I have a backup of it, when i flashed the recovery the first time... with heimdall.
ps: I smashed it a little bit... with such things in mind, you can go crazy about... or just ignore your private life and give it to google, samsung & more
I would really like to see the bigdata databases from millions of people profiled in a neat profile... with everything in it. Just use a search tool like everything and find instantly a person with the attributes you seek. Clever Controlfreaks
Ok f*ck that.. lets get a life and just fix the problem
Still the same thing...
I need to clean everything, except my data, like photos and my cwm backup. and to install a clean system.
How can I do this with only download modus avaiable?

[GUIDE] Flashing ROMs to the Vivo Air

Alright, so following some prodding, searching, and questioning, I flashed MIUI V6 to my BLU Vivo Air alongside TWRP.
I will update this post with a detailed, step-by-step guide including my own personal mirrors for your convenience and those of you without 4PDA accounts, which is the Russian equivalent of XDA.
Upon booting, I noticed apps force closing without being launched. Namely Hangouts and Newsstand. I'm sure reinstalling them will resolve the issue rather quickly.
Stay tuned for updates.
Update 1:
TWRP had difficulty mounting data and cache for me, and was unable to format them. This led to applications force closing, window mishaps, and accounts glitching out. I just flashed Carliv recovery, and flashed MIUI with it. Flashing gapps at the moment, and will update you on my progress.
Update 2:
Currently attempting to format data (success), cache (success), and dalvik (success).
Update 3:
Rebooting into MIUI V6, checking if I've entered a bootloop.
5 seconds - Boot animation reached, "MIUI Pro."
165 seconds - Still booting.
180 seconds - Setup screen reached, MIUI V6 flashed successfully.
Update 4:
Google apps flashed successfully, no redraws or force closes this time. Had an issue with the keyboard not registering as being selected, Google voice typing appeared as the default. Pull down notification shader and "choose input method" to select MIUI Smart Keyboard. Signed into Google successfully. Will run preliminary tests on video playback, camera, and multitasking.
Guide:
If you mess up your phone, it is on you, and I am not to be held liable for your actions. This is your responsibility. A lack of planning on your part does not constitute an emergency on mine. With that out of the way, if you encounter troubles, I am more than happy to help you.
Step 1:
Root your phone using one of the links provided. Click HERE for method 1, or HERE for method 2. I personally used method 1 because it was the first I saw. They both get the job done.
Step 2:
Install THIS application (Settings -> Security -> Unknown Sources), and install a recovery. I installed Carliv recovery, and had no problems with it. You can also install TWRP, however, it had issues mounting data and cache. This left it unable to factory reset when I flashed MIUI, which subsequently led to problems. I do not recommend flashing TWRP - You have been warned. Carliv recovery says it can't "mount" cache, although when formatting it does so without a problem. I believe Carliv is supposed to be touch-based, although the touches weren't responding for me. The controls are as follows: Volume +/- for navigating, Power for selecting, and the Back key for, you guessed it, going back.
Step 3:
Install MIUI V6, located HERE, and then install Google Apps, located HERE. After installing, factory reset the device from recovery and reboot into the system. I posted my timestamps at the top of the post, so you can get an idea of how long your flash/boot process should take.
Step 4:
Basic setup. Be ready to fix your keyboard if you had the same issue I did, which isn't even necessarily a problem. Choose WLAN network and sign into your accounts, then you're good to go.
To root the ROM, I recommend finding "iRoot" for your computer. Then boot to recovery and install the SuperSU zip, as it's better than the root app which comes with the iRoot method.
Enjoy your ROM, and be sure to thank our Ruski comrades over at 4PDA!
Special thanks to @DvDwx. (research), @itsJohnuno (answers), and @Milly7 (testing).
All download links are being hosted by me, and I recommend creating mirrors of your own as safety precautions in the event that the files are removed or become unavailable.
Have a phenomenal day or night, possibly even both. If you have any questions, I'll do my best to answer them.
Nice Guide ;D
DvDwx. said:
Nice Guide ;D
Click to expand...
Click to collapse
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
DvDwx. said:
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
Click to expand...
Click to collapse
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Ilxaot said:
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Click to expand...
Click to collapse
i understand that ;D
on my WonderMedia WM8880 Tablet project i share the projects from other developers... but i asked they to have permission to share that, and leave on post the credits with their names... maybe if you talk with developer on 4PDA for permission to do it or ask him if it is possible he share he ROM Project here is will be perfect... anyway Good Guide to Flash this ROM :highfive:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
dimasp6 said:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
Click to expand...
Click to collapse
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
DvDwx. said:
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
Click to expand...
Click to collapse
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
dimasp6 said:
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
Click to expand...
Click to collapse
You can also try iRoot. Install SuperSU and try using it as the root granter for the recoveries.
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
ron580 said:
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
Click to expand...
Click to collapse
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Ilxaot said:
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Click to expand...
Click to collapse
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
ron580 said:
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
Click to expand...
Click to collapse
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Ilxaot said:
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
request
Ilxaot said:
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
JesusEMC said:
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
Click to expand...
Click to collapse
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
on Captcha you need count the numbers and ignore the russian Letters Like for exemple -> ##22###16## -> 22+16= 38
to can finish the registration... and no, you don't need use VPN or Proxy to create the account :highfive:
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
itsJohnuno said:
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
Click to expand...
Click to collapse
Our Buddy @SSJGohon found the kernel source code and already shared on some topic(i Already re-shared that on Cyanogen Mod to Mediatek SoC's Development thread... but anyone there say nothing about it... and already shared on 4PDA to maybe the MiUi developer can Bring something to All...). i already downloaded and already start my research about what can be maked with that and for sure have a possibility to we have a custom Kernel and maybe Custom ROM like PURE AOSP, AOSPA... but Cyanogen Mod is more difficult because we don't have a updated Repo Source from MediaTek to work like Driver Blobs to GPU, Bluetooth, Wifi Drivers... etc
My real problem is i don't have all skills to make a custom kernel to Mediatek SoC because a lot of things change from Qualcomm to Mediatek.. but if anyone here want to try development that just search the topics with @SSJGohon comments replays :highfive:
Ilxaot said:
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
Click to expand...
Click to collapse
I've already installed the ROM, it runs smoothly! You were right, I really like it! I had an issue trying to format /data, it took like 15 minutes, and did a hard reset (pressed power button for a few seconds) and tried to format again and it worked. Im a little bit worry cause I've had 2 radom reboots so far.. Any idea of what has happened to me?

Root Asus Memo Pad 176 on lollipop .36 newest firmware plus Xposed

***DISCLAIMER***
If done incorrectly, this can soft brick your device. I take no responsibility for this, and if you're unfamiliar with rooting android I suggest reading up before attempting. There are threads to fix your tablet if this goes sideways, but if this doesn't work I personally can't promise I can help you.
I used this method two days ago, and would like to thank jerbear294 for providing me with the information. I didn't come up with this, I just want to help others looking for root.
Hello guys
First, apologies if this is a redundant thread. All the root methods I've seen in individual topics seem outdated, and I just wanted to make this quick guide to help people from having to scan through pages of information to learn how to root these things. This method works on firmware WW_V12.10.1.33_20150917, which is the current release as of this post.
Lets get to it!
Download
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
(Navigate to page 1, for some reason it links to the last page)
Place it on your computer and unzip.
And the latest supersu .zip 2.46
https://download.chainfire.eu/696/supersu/
Which will be on your tablet.
Install the temp recovery to your computer, connect the tablet, make sure you enable adb (USB Debugging) on it in developer mode (Settings → about → software version → tap build number 7 times for developer mode). Once connected, run the exe in the .zip from the temp recovery.
Choose: TWRP HDPI portrait, T4.
Your device will boot into twrp recovery. Now navigate to the supersu.zip on your tablet, and install, and you should be good to go . Good luck, and happy rooting!
Thanks to everyone who developed these tools (especially Social_Design_Concepts), and XDA for providing a medium to relate them.
To run Xposed, go to http://forum.xda-developers.com/showthread.php?t=3034811
Choose 'xposed-v80-sdk21-x86', this is currently the only version I've had success with. Happy hunting folks!
404 page not found on the first link?
ThunderThighs said:
404 page not found on the first link?
Click to expand...
Click to collapse
Link fixed, thanks and my apologies
thank you a lot! you saved me a lot of browsing! :good:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
seamo123 said:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
Click to expand...
Click to collapse
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Opensystem said:
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Click to expand...
Click to collapse
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to create a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Then I placed all the files from the nandroid zip inside that (second) folder. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
I wonder should I have taken the recovery log from my own nandroid and replaced jerbear's recovery log with it? I'm starting to confuse myself at this point I think..
seamo123 said:
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to unzip the file into a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
Click to expand...
Click to collapse
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Opensystem said:
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Click to expand...
Click to collapse
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Yes the general for the memo 176 has a special working xposed, make sure you use that one. I'm a bit busy, but I'll link when I can glad you got it rooted
Joe_Bangles said:
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
Click to expand...
Click to collapse
Glad to help, xda is where it's at for community
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Delichi said:
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Click to expand...
Click to collapse
Hurray! Glad it worked out for you
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Hey sorry for the late response, work got crazy on me. I edited the original post to now include how to set up Xposed, for you or anyone else interested. Confirmed working on both .33 and .36
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
dareas said:
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
Click to expand...
Click to collapse
It's got less battery drain here, performance seems better too but that could just be a placebo
Opensystem said:
It's got less battery drain here, performance seems better too but that could just be a placebo
Click to expand...
Click to collapse
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
dareas said:
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
Click to expand...
Click to collapse
I'm not sure, we should be because of art runtime but I feel like our version is bootlegged to a degree
unable to mount /data, internal storage 0MB. How can I load the zip file?
It's probably because FDE. I used a external SD card instead

Categories

Resources