I did something incredibly stupid. Please help me out. I have a Redmi 2 Pro, and for a while, Google Camera was not working as before, and I was always looking for a fix, and then I found one: I have to add "ro.config.low_ram=false" to the build.props file.
I copied this file to I think "/storage/emulated/0/" ,edited it, and then copied it back to /system/, and then I restarted my phone, and now only the MI logo comes up.
I don't know much about Android and I've really never should have experimented with my own phone like this, I feel really stupid. This is the first time ever (probably also the last) when I do anything that needs root. I hope you can help me out! What should I do?
Argentoratum said:
I did something incredibly stupid. Please help me out. I have a Redmi 2 Pro, and for a while, Google Camera was not working as before, and I was always looking for a fix, and then I found one: I have to add "ro.config.low_ram=false" to the build.props file.
I copied this file to I think "/storage/emulated/0/" ,edited it, and then copied it back to /system/, and then I restarted my phone, and now only the MI logo comes up.
I don't know much about Android and I've really never should have experimented with my own phone like this, I feel really stupid. This is the first time ever (probably also the last) when I do anything that needs root. I hope you can help me out! What should I do?
Click to expand...
Click to collapse
Do you have access to TWRP?
Dan_Jacques said:
Do you have access to TWRP?
Click to expand...
Click to collapse
Yes, I've managed to solve it in the end by installing TWRP and chmodding build.prop from there, so my phone is working again! Thank you for your help.
Argentoratum said:
Yes, I've managed to solve it in the end by installing TWRP and chmodding build.prop from there, so my phone is working again! Thank you for your help.
Click to expand...
Click to collapse
But dont stop do anything that's need root. Sometimes u make a mistake, me too.
When for the first time I flashed custom ROM, I DID NOT INSTALL CUSTOM RECOVERY. And I brick my phone just like u. I brick my phone 5 times. fortunately I have a backup.
Soooo, don't stop modifying !
Related
Hey there, I recently purchased a Bell Atrix 4G. I rooted it and everything was going fine, so I thought I'd try the gingerblur rom for the device, the tutorial site didn't mention anything about not using it on a Bell Atrix, which I found out later was a bad idea (I did make a backup though at the backup prompt). So needless to say the phone is now at the "M screen flashing red led boot loop". What I wanted to know, is if that since I have access to fast boot, if there's any way to restore from that backup.tar file, or if I can use an at/t sbf file to restore to (I didn't try it in fear of making things worse). Thanks in advance!
Grimacexl said:
Hey there, I recently purchased a Bell Atrix 4G. I rooted it and everything was going fine, so I thought I'd try the gingerblur rom for the device, the tutorial site didn't mention anything about not using it on a Bell Atrix, which I found out later was a bad idea (I did make a backup though at the backup prompt). So needless to say the phone is now at the "M screen flashing red led boot loop". What I wanted to know, is if that since I have access to fast boot, if there's any way to restore from that backup.tar file, or if I can use an at/t sbf file to restore to (I didn't try it in fear of making things worse). Thanks in advance!
Click to expand...
Click to collapse
Whatever you do DO NOT USE THE ATT SBF! That is not meant for bell devices and will definetly make your situation even worse!
Yeah, I figured that would be the case.
Working on trying to push my backup files to my device atm
Grimacexl said:
the tutorial site didn't mention anything about not using it on a Bell Atrix,
Click to expand...
Click to collapse
dude, it's in CAPITAL RED LETTERS on both the tutorial website and the forum thread.
this guy had a similar situation, but i don't know if he got it fixed.
http://forum.xda-developers.com/showthread.php?t=1033184&highlight=bell+sbf
EDIT: attached
Yeah, the tutorial I used didn't say to not use it on bell atrix, but when it messed up, I went to all the other tutorials that have it in red, so I do feel pretty stupid.
Well, it's all good now, After pushing bell backup app and framework folders, I managed to get a working device (all be it with some force close crap which I'll iron out later) The device is working.
***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
Hi all, i'm new to Android Phones, so i started a few days with this phone. But now i think i've done a big mistake, i tried to erase everything from the phone, in a hope to "restore" to the factory state. Instead, i think i've deleted everything from the phone, and now, it only says "Your device is booting now..." and it doesn't boot. It's unlocked and rooted, i've deleted it from the TWRP menu.
So, is there anything that i can do, to restore it back? The model i think it's the VNS-L31, i'm downloading a firmware from the L21, can it be replaced or something like that? Thankx in advance.
*Edit* I found stock rom for my phone here in the fórum, but it says i need to have stock recovery but i have the TWRP recovery. Is there any way that i can do it, with that recovery?
*Edit 2* In Erecovery, when i try to download it says "Getting package info failed"
First of all... Why don't you have a backup in TWRP? ALWAYS back up your stuff before doing ANYTHING in TWRP.
Second: there is an option for factory reset within the EMUI system itself. Absolutely no need to mess around in TWRP for something like that. Of course you can "factory reset" in TWRP but this can also wipe your system which then requires you to flash something.
To your problem:
Since I luckily was not forced to flash a stock firmware yet, some more information would be nice.
In which format does the firmware come (link to where you downloaded it)? TWRP can handle .zip files. So if it comes as a .zip file, you can try flashing it through TWRP (really depends on what you downloaded!)
If you only need stock recovery, try accessing TWRP with your phone plugged into a PC.
This way it normally fires up the stock eRecovery.
Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.
iDeadSmack said:
Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.
Click to expand...
Click to collapse
Hmm maybe best way is to send the user that made it work a PM and maybe he can provide you a guide on how to do it.
And maybe he or you can then provide a guide here on how to do it.
This device is rather new and the forum is building up so there is a lot of work to do and a lot of things have to be worked around.
Hope you can fix it, like I said, I cannot really help you properly since I never had the problem and therefore do not really understand what's happening on your device.
hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You
iDeadSmack said:
hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You
Click to expand...
Click to collapse
Could you help me with this problem i have the same problem on Huawei l-21 ??
Always have a backup of your fresh system on TWRP. Then whatever happen just restore it whenever you think you messed up your device and you should be fine ALWAYS.
Hi, first, sorry for my english, is not perfect.
Days ago i was trying to fix the network problem on my Huawei, and some audio problems too, Mixer paths and some issues. About the network issue, i flashed an zip that supposedly could fix the problem. In this case, I was not completely sure so i made a backup of all on TWRP of course... But surprise, when it finished i pressed reboot system and thats all. The phone died. There is no answer to charge, no answer to PC, no vibration, no led, no screen boot, logos, nothing.
I will leave the link of the zip here if somebody with more knowledge can take a look and help, thanks...
http://www.mediafire.com/download/sdwoyft9p7rccyr/Archivos+Galaxy+S3.rar
ThugMaster said:
Hi, first, sorry for my english, is not perfect.
Days ago i was trying to fix the network problem on my Huawei, and some audio problems too, Mixer paths and some issues. About the network issue, i flashed an zip that supposedly could fix the problem. In this case, I was not completely sure so i made a backup of all on TWRP of course... But surprise, when it finished i pressed reboot system and thats all. The phone died. There is no answer to charge, no answer to PC, no vibration, no led, no screen boot, logos, nothing.
I will leave the link of the zip here if somebody with more knowledge can take a look and help, thanks...
http://www.mediafire.com/download/sdwoyft9p7rccyr/Archivos+Galaxy+S3.rar
Click to expand...
Click to collapse
At the very least you have overwritten the kernal and the modem partitions but its anybodys guess where the patches were ACTUALLY written to, considering the Zip is meant for a Galaxy S3 !!
What were you thinking of when you thought that this could fix anything on a Huawei ?
Sparkrite said:
At the very least you have overwritten the kernal and the modem partitions but its anybodys guess where the patches were ACTUALLY written to, considering the Zip is meant for a Galaxy S3 !!
What were you thinking of when you thought that this could fix anything on a Huawei ?
Click to expand...
Click to collapse
It was a desperate attempt to fix the mobile network, a thing that a real need, and the video of the zip supposedly could fix it, and doesnt say that was only for S3, but, even so i made the backup of everything for that reason, because i dont know what im really flashing.
ThugMaster said:
It was a desperate attempt to fix the mobile network, a thing that a real need, and the video of the zip supposedly could fix it, and doesnt say that was only for S3, but, even so i made the backup of everything for that reason, because i dont know what im really flashing.
Click to expand...
Click to collapse
A little bit of a give away is in the title of the zip file ie. ".........Galaxy+S3.......", don't you think ?
However if your phone is totally dead and not been "seen" by a PC with the appropriate drivers loaded then its back to base I'm afraid, or maybe explore here:-
https://hcu-client.com/
Sparkrite said:
A little bit of a give away is in the title of the zip file ie. ".........Galaxy+S3.......", don't you think ?
However if your phone is totally dead and not been "seen" by a PC with the appropriate drivers loaded then its back to base I'm afraid, or maybe explore here:-
https://hcu-client.com/
Click to expand...
Click to collapse
I cant do anything. The phone was perfectly connected to PC with the adb-fastboot drivers, usb drivers, even Hisuite. The deal, as i said, is that the phone is completely dead.
I tried to flash it but it only bootloops for me. Have tried almost everything it seems. Have never had so much trouble flashing a phone.
I have tried Lieage os 15.1 but after i tried to flash N2G48B_4Cores.img from this side https://www.xda-developers.com/nexus-6p-bootloop-fix/ Lineageos bootloops even faster. Even tried the twrp from the side who requires a password I cant find so it it is useless.
I have tried Aquatios but it bootloops.
I have tried to flash stock android but it says something about the zip is wrong.
Someone who knows what I should do or am I stuck? I forgot to make a backup to so I am a bit desperate. Never forget it usually but only because it's not my phone I do forget.
I hope someone knows what I should do.
*EDIT* [SOLVED]
Trie this and got a bit further: https://forum.xda-developers.com/ne...t/rom-lineageos-16-0-nexus-6p-angler-t3849169
Only that the screen flashes soon after after the settings come up and turn itself of after a while.
I have not flashed the radio though. Is that necessary?
*EDIT 2* [NOT SOLVED]
The radio were necessary for wifi.
Now is the problem with signing in to google.
Never can anything go smoothly.
I solved it finally. Will remove the thread as soon as I see how I do. Have not used xda in a while.
orrebo said:
I solved it finally. Will remove the thread as soon as I see how I do. Have not used xda in a while.
Click to expand...
Click to collapse
Good to hear. So what did you do wrong and what did you do to fix it?
Aimless Rambler said:
Good to hear. So what did you do wrong and what did you do to fix it?
Click to expand...
Click to collapse
Yeah. What did I do. Tried until I found a solution that worked. Think I mentioned it (did not). This thread I looked at to solve that problem: https://forum.xda-developers.com/ne...t/rom-lineageos-16-0-nexus-6p-angler-t3849169
I had to flash a bootloader file and after that it worked better.
But I can't sign in to google how I do. Will try a couple of other gapps. Hopefully someone will work.
I have seen this before but don't remember how I solved it back then.
It even bootloops if it don't like the gapps.
New problems every time. A new one again where it crashes in the initial settings.
It stopped suddenly and is now back to checking info and this time it said it can't connect to google servers.
Have never ever worked with such a ****ty phone.
*EDIT*
I give up. It is as good as it gets.
If someone else of her friends wants to try so be my guest.
Over and out for this time.
If it's toast from the infamous bootloop issue can't blame you for setting the phone aside. But if you venture back to it I'd suggest flashing stock Google firmware then doing the 4cores fix if needed.