Database Info

[Q][ANSWERED] Gaining root access... Fail!

Hi. I have searched the forums and have yet to find an answer to my question. I tried following this tutorial (CWM 6.0.2.3 / 5.5.0.4 Official CWM Recovery for JB/ICS + ROOT) to root my TF300. It's gone pretty well, except it doesn't actually give me root access. I'm not really sure what's going wrong. I unlocked and installed CWM (recovery-jb.img) fairly easily. I flashed root-signed.zip and it says everything's ok until I try rebooting, whereupon it gives me the following error:
"root access possibly lost. fix?"
I tried both yes and no, but after each time, I try a root checker, and try updating su over and over again, but no dice. Am I doing anything wrong?
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

First off try using TWRP instead of CWM. Not only are people having issues rooting using CWM, some are also having trouble making backups. TWRP is definitely the way to go. Its more dependable and the UI (user interface) is much better.
As for rooting, why not just install a stock based custom ROM that's already rooted?
Sent from my LG-LG855 using Xparent Green Tapatalk 2

Trying It Out As We Speak...
wetbiker7 said:
First off try using TWRP instead of CWM. Not only are people having issues rooting using CWM, some are also having trouble making backups. TWRP is definitely the way to go. Its more dependable and the UI is much better.
As for rooting, why not just install a stock based custom ROM that's already rooted?
Sent from my LG-LG855 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Giving it a try. Fastbooting TWRP 2.3 (www(.)teamw(.)in/project/twrp2/97) as we speak. Im fairly new to rooting and just started researching it yesterday. Most tutorials show CWM so I used it. Love the TWRP UI in the screenshots. Never knew there were more options.
And another question; will installing a stock rooted ROM whipe my data?

MrSantos1231 said:
Giving it a try. Fastbooting TWRP 2.3 (www(.)teamw(.)in/project/twrp2/97) as we speak. Im fairly new to rooting and just started researching it yesterday. Most tutorials show CWM so I used it. Love the TWRP UI in the screenshots. Never knew there were more options.
And another question; will installing a stock rooted ROM whipe my data?
Click to expand...
Click to collapse
Yes, you will want to do a factory reset 1st before flashing anything. You do not want any data that may have gotten left over to be on the new ROM. I also recommend wiping the cache and Dalvik cache too.
All you need to do in order to restore your contacts is to sign in to the market or Gmail.

[ANSWERED] Gaining root access... Fail!
wetbiker7 said:
Yes, you will want to do a factory reset 1st before flashing anything. You do not want any data that may have gotten left over to be on the new ROM. I also recommend wiping the cache and Dalvik cache too.
All you need to do in order to restore your contacts is to sign in to the market or Gmail.
Click to expand...
Click to collapse
I really didnt want to whipe my data, so I went on the SuperUser website and got the binary update, and installed it from TWRP and violla! It actually worked. Thanks for your help.
-----------------------------------------------------------------------------------------------------
INCASE SOMEBODY ELSE READS THIS POST:
How I Rooted My TF300 Without Problems:
Unlock device with bootloader.
Install fastboot package here: www(.)mediafire(.)com/?9ylow29klhccc0x
Download TWRP blob here: www(.)teamw(.)in/project/twrp2/97
Extract the folder holding Fastboot to your C drive.
Place the TWRP Blob in the Fastboot folder, and re-name the file twrp.blob.
Fastboot the blob to your device. (Use video below for guidance)
Once device is rebooted, download and flash the zip located here: bit(.)ly/TlIUdE
Thats It. :highfive:
www(.)youtube(.)com/watch?v=3OsS0qEGocE
Disclaimer: Cant paste actual links. I need 10 or more posts.

Excellent! I cannot count the times I've recommended members to switch over to TWRP in that past few days. It really is a better recovery. Many are having issues with CWM. Glad you got it working. :good:
If I were you, I would make a backup with TWRP as soon as you can.
Just remember that if you DO decided to flash a custom ROM, make sure that you do a factory reset, wipe cache, and Dalvik cache. There's a very good chance you'll have problems if you don't. :good:

Aye.
wetbiker7 said:
Excellent! I cannot count the times I've recommended members to switch over to TWRP in that past few days. It really is a better recovery. Many are having issues with CWM. Glad you got it working. :good:
If I were you, I would make a backup with TWRP as soon as you can.
Just remember that if you DO decided to flash a custom ROM, make sure that you do a factory reset, wipe cache, and Dalvik cache. There's a very good chance you'll have problems if you don't. :good:
Click to expand...
Click to collapse
I backed up using TWRP fairly easy as soon as I got most of my rooted setting up and running. Whenever I have a problem, the first thing I do is wipe them both. After some more research, I'll get into some ROMS with backups now that I am able to do some nandroids. Thanks again. :victory:

I think I may have messed up putting a new ROM on my phone

So I'm still extremely new to rooting/ROMS/ODIN etc. Well I finally decided to throw caution to the wind and attempt to root and install Slim Bean on my phone. Honestly I think because most help sites can't keep up to date with all the current ROM updates and what not that I may have messed something up. Also, before anyone rips my head off, I tried to post this question in the developers thread but I'm still to new. Anyways here's what I did:
Downloaded ODIN v1.85, SkyrocketCWMrecovery.tar, Slim Gapps and Slim-i727-3.1.0-OFFICIAL
I first ran ODIN (left all the check boxes alone as they appear when you start up), chose PDA, and chose SkyrocketCWMrecovery.tar to install.
Preformed install and rebooted my phone, everything works fine
Put Slim Gapps and Slim I727-3.1.0 onto my Internal SDCard
Disconnected phone from USB and started CWM (the version CWM is v5.0.2.6)
I wiped data/factory reset and under mounts and storage format/system
Then I installed Slim I727-3.1.0 and Gapps
I rebooted my phone and it starts loading, gets to the slim bean screen and stops
I've also tried Cyanogenmod 9.1 and 10. 9.1 does the same thing Slim bean does and 10 gets an Status 7 error, Installation aborted. I've read so many posts about this but nothing has seemed to fix my issue, at this point I would happily go back to a stock phone (I wish I'd just backed it up when I had the chance, live and learn I guess)
If someone can please help me, I'd really appreciate it.

Why using a Old Reciovery?
Head to ClockworkMod v6.0.2.7 Touch v14.4.6
Download the Latest Touch Recovery File and put it on your Sd Card and flash it Via Recovery.
After that Boot into Recovery
Format system (usually in mounts and storage menu option) X3
Format data X3
wipe data and cache partition X3
After that Flash the Rom.
In case if the Issue still persists revert back to Stock and Try Again..

manu44 said:
Why using a Old Reciovery?
Head to ClockworkMod v6.0.2.7 Touch v14.4.6
Download the Latest Touch Recovery File and put it on your Sd Card and flash it Via Recovery.
After that Boot into Recovery
Format system (usually in mounts and storage menu option) X3
Format data X3
wipe data and cache partition X3
After that Flash the Rom.
In case if the Issue still persists revert back to Stock and Try Again..
Click to expand...
Click to collapse
Ok, I got it to flash to the new version (the website I was using had the download for the old version I was using). However, when I try to wipe data and cache partition it tries to preform the action but it just sits on the screen saying formatting data....
I tried just loading cyanogenmod 10 on there and see if I got lucky, with the new version I can get the zip file to install but when I tried to reboot I get to the cyanogenmod screen and it just sits there..... any ideas?

You have to start learning doing things in the "correct" and "safe" way ..
1.Leave all other websites and stick here for the flashing and roms and what not.
2.Never use ODIN for anything ever (except for flashing stock ROM)
3.An exception also for using ODIN is the bone stock phone , you'll need ODIN to just flash a custom recovery in .tar format (this is usually just done once , even if a new recovery comes out , you update it also from a custom recovery) , once your device has a custom recovery (and a recent one) do everything from there as the custom recovery enables you to do everything from inside the recovery ..
4.Learn from the stickies here on the skyrocket section .

drkreign said:
Ok, I got it to flash to the new version (the website I was using had the download for the old version I was using). However, when I try to wipe data and cache partition it tries to preform the action but it just sits on the screen saying formatting data....
I tried just loading cyanogenmod 10 on there and see if I got lucky, with the new version I can get the zip file to install but when I tried to reboot I get to the cyanogenmod screen and it just sits there..... any ideas?
Click to expand...
Click to collapse
Ill recommend you to Flash Back to Stock Rom and then Try again.. with the Latest Recovery file

manu44 said:
Ill recommend you to Flash Back to Stock Rom and then Try again.. with the Latest Recovery file
Click to expand...
Click to collapse
Awesome, my phones back. As for trying again, I'm thinking I may skip that lol. I came from a jailbroken Iphone to trying this on my android but the android is 10x more complicated (read: way more options/routes to go to do the same thing, which is way to confusing for the first timers). Thanks for all your help!

mahanddeem said:
You have to start learning doing things in the "correct" and "safe" way ..
1.Leave all other websites and stick here for the flashing and roms and what not.
2.Never use ODIN for anything ever (except for flashing stock ROM)
3.An exception also for using ODIN is the bone stock phone , you'll need ODIN to just flash a custom recovery in .tar format (this is usually just done once , even if a new recovery comes out , you update it also from a custom recovery) , once your device has a custom recovery (and a recent one) do everything from there as the custom recovery enables you to do everything from inside the recovery ..
4.Learn from the stickies here on the skyrocket section .
Click to expand...
Click to collapse
Again, still new, but I don't think I used ODIN for anything other than installing the CWM recovery and even doing that (notably was directed to an older version) the ROMs wouldn't take. Even after upgrading the CWM to most updated version it still failed to get any version of cyan 9-10 or slim bean to work, all of them get to their respective screens and load. I even got tired, went to bed and 7 hours later the phone still wouldn't boot.
As far as I can tell I did everything this website has said to do, unless you can point me to something otherwise? Not to be rude, just trying to figure out where I would have messed up, but I just can't see where I'd have messed up OTHER than running a old version of CWM. But even that was corrected with an update and still I received the same results.

drkreign said:
Again, still new, but I don't think I used ODIN for anything other than installing the CWM recovery and even doing that (notably was directed to an older version) the ROMs wouldn't take. Even after upgrading the CWM to most updated version it still failed to get any version of cyan 9-10 or slim bean to work, all of them get to their respective screens and load. I even got tired, went to bed and 7 hours later the phone still wouldn't boot.
As far as I can tell I did everything this website has said to do, unless you can point me to something otherwise? Not to be rude, just trying to figure out where I would have messed up, but I just can't see where I'd have messed up OTHER than running a old version of CWM. But even that was corrected with an update and still I received the same results.
Click to expand...
Click to collapse
Also, not sure if anyone else is having this issue but when I try to format cache, either using wipe data/cache partition or going under mounts and storage format cache it locks up. Does data just fine but cache is a no go. I'd mention this in the development section but not enough post counts.

mahanddeem said:
4.Learn from the stickies here on the skyrocket section .
Click to expand...
Click to collapse
+1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Always read the stickies. Always read the stickies. Always read the stickies.
This is a magical mantra, if typed three times it comes true))

If you're having trouble with cwm, try flashing twrp. I find that it is easier to use for the basics.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

If your recovery is up to date and its just bootlooping after flashing, reboot into recovery and wipe cache & dalvik cache.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

[Q] Help: Nexus 5 bricked while clearing Cache Partition

I was on Android 4.2.2 STOCK recovery and Rooted with Chainfire's Auto Root. Had sideloaded the 4.2.2 update.
I was stupid and I booted into Bootloader mode (Power+volume up + volume down)
Then I cleared Cache Partition. (not factory reset). On doing that, nothing happened for 10 minutes. The message was "Formatting Cache" I then switched off my phone.
Since then nothing is working. I cannot connect to phone network. The SD card folder is not working.
I went into Bootloader, and get the following error:
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
______________________
I've tried sideloading OTA update files, but I get the same error above. On factory Reset/Data -- I get the same error. I cannot do anything at this point. As before I am on STOCK recovery.
Someone kindly help. Is my phone bricked. I am so nervous.
Everything was perfect until I cleared the Cache partition.
Thank you so much. I hope someone replies soon.

http://forum.xda-developers.com/showthread.php?p=48360203
You can fastboot flash cache.IMG from the stock image to fix the corrupted cache partition.
Sent from my Nexus 5 using xda app-developers app

xybur said:
http://forum.xda-developers.com/showthread.php?p=48360203
You can fastboot flash cache.IMG from the stock image to fix the corrupted cache partition.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thank you so much. The linked thread talks about the same problem I am having.
Could you please point me to instructions on where to get Cache.IMG from the stock Image? Is it ok to fastboot flash Cache.IMG from 4.4.0 or is there a Cache.IMG for 4.4.2 as well?
Thanks.

If you download the stock image from the Google Dev site, its in there.
https://developers.google.com/android/nexus/images
You will need 7zip or a similar program to read the contents of the file. Just keep unzipping until you find the directory with the cache.img file (there should also be a radio.img, bootloader.img, etc. Basically, all of the stock files. You're only interested in the cache.img file in this instance).
I flashed it after I did the 4.4.1. Ota update so you should be fine too fast boot flashing it as well.
Sent from my Nexus 5 using xda app-developers app

I had the exact same problem, so i did a factory reset and everythin went bak to normal.only thing had to reroot

This isn't 100% I've done this and full factory rest I ended up having to rma PS I had my Efs also it still didn't work my logs said that it couldn't create the SD partion because my system was read only so I'm without my phone for two weeks
Sent from my Desire HD using Xparent Green Tapatalk 2

xybur said:
You will need 7zip or a similar program to read the contents of the file. Just keep unzipping until you find the directory with the cache.img file (there should also be a radio.img, bootloader.img, etc. Basically, all of the stock files. You're only interested in the cache.img file in this instance).
I flashed it after I did the 4.4.1. Ota update so you should be fine too fast boot flashing it as well.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thank you. Just downloaded the Cache.IMG file. And then placed it into the directory where the Android Fastboot is installed.
What should be the exact command for using Fastboot flash on Cache.img?
"fastboot flash cache Cache.IMG"
Is there anything else to it? Thanks in advance.

iamjimmy said:
Thank you. Just downloaded the Cache.IMG file. And then placed it into the directory where the Android Fastboot is installed.
What should be the exact command for using Fastboot flash on Cache.img?
"fastboot flash cache Cache.IMG"
Is there anything else to it? Thanks in advance.
Click to expand...
Click to collapse
Should be it.
Code:
fastboot flash cache cache.img
while in bootloader mode. make sure "fastboot mode" is displayed in the bootloader. i.e.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

xybur said:
Should be it.
Code:
fastboot flash cache cache.img
while in bootloader mode. make sure "fastboot mode" is displayed in the bootloader. i.e.
Click to expand...
Click to collapse
Thank you so so much. I did this yesterday. It worked like a charm. I took the Cache.Img file (13 mb) from the stock Android 4.4 factory Image.
Then phone booted immediately and everything seems fine. I was still on 4.4.2 and did NOT even lose the root.
The only thing messed up was the notifications. I had to set the notification ringtone and also reintegrate Google voice voicemail. Everything else is perfect.
I really can't thank you enough. Much appreciated.

iamjimmy said:
Thank you so so much. I did this yesterday. It worked like a charm. I took the Cache.Img file (13 mb) from the stock Android 4.4 factory Image.
Then phone booted immediately and everything seems fine. I was still on 4.4.2 and did NOT even lose the root.
The only thing messed up was the notifications. I had to set the notification ringtone and also reintegrate Google voice voicemail. Everything else is perfect.
I really can't thank you enough. Much appreciated.
Click to expand...
Click to collapse
Another way to do this is to actually go back and clear the cache partition again. I had the exact same issue and thought that I was bricked until I went back and tried it again. Be patient, mine took between 10-15 minutes but eventually finished and everything was fine again.

iamjimmy said:
I really can't thank you enough. Much appreciated.
Click to expand...
Click to collapse
Not a problem, glad to be of service
---------- Post added at 07:33 PM ---------- Previous post was at 07:33 PM ----------
iboj007 said:
Another way to do this is to actually go back and clear the cache partition again. I had the exact same issue and thought that I was bricked until I went back and tried it again. Be patient, mine took between 10-15 minutes but eventually finished and everything was fine again.
Click to expand...
Click to collapse
If the cache is corrupt, it might not even be able to be mountable. YMMV, but when it happened to me, in my case, I had to use the fastboot flash method.

iboj007 said:
Another way to do this is to actually go back and clear the cache partition again. I had the exact same issue and thought that I was bricked until I went back and tried it again. Be patient, mine took between 10-15 minutes but eventually finished and everything was fine again.
Click to expand...
Click to collapse
I tried doing that. But like in the previous post, the Cache is not mountable or corrupt maybe. Nothing really happened when I did wipe cache partition. It kept giving that error about Cache not mounted.

iamjimmy said:
I tried doing that. But like in the previous post, the Cache is not mountable or corrupt maybe. Nothing really happened when I did wipe cache partition. It kept giving that error about Cache not mounted.
Click to expand...
Click to collapse
Have you tried to fastboot flash the cache.img?

jd1639 said:
Have you tried to fastboot flash the cache.img?
Click to expand...
Click to collapse
Yes. That's what Actually worked. Thanks to the guidance of user: xybur.
However I Flashed the Cache from the stock image on 4.4 Kitkat from Google servers on a phone which has been updated to Android 4.4.2.
I was not able to find the cache.img file in the OTA updates of 4.4.1 and 4.4.2 downloads.
So in other words, I have Android 4.4.2 but the Cache.img file flashed from Android 4.4 (base release). Not sure whether that would lead to problems down the road.
Also is clearing the cache partition ALWAYS recommended before sideloading an OTA update manually?

iamjimmy said:
Yes. That's what Actually worked. Thanks to the guidance of user: xybur.
However I Flashed the Cache from the stock image on 4.4 Kitkat from Google servers on a phone which has been updated to Android 4.4.2.
I was not able to find the cache.img file in the OTA updates of 4.4.1 and 4.4.2 downloads.
So in other words, I have Android 4.4.2 but the Cache.img file flashed from Android 4.4 (base release). Not sure whether that would lead to problems down the road.
Also is clearing the cache partition ALWAYS recommended before sideloading an OTA update manually?
Click to expand...
Click to collapse
You're fine. If you were really worried about it you could flash the 4.4 to 4.4.2 zip that's in the general forum ota sticky. That zip patches, it's not the full rom, 4.4. I don't remember if there are any cache patches in it though. As far as clearing the cache before the ota, I've never done that and haven't had any problems.

jd1639 said:
You're fine. If you were really worried about it you could flash the 4.4 to 4.4.2 zip that's in the general forum ota sticky. That zip patches, it's not the full rom, 4.4. I don't remember if there are any cache patches in it though. As far as clearing the cache before the ota, I've never done that and haven't had any problems.
Click to expand...
Click to collapse
Thanks. I did search the 4.4.2 big zip file which is supposed to patch from 4.4 to 4.4.2. I did not find a cache.img in that file. So it seems there is no new cache, so I guess Google patched the existing one.
In any case my phone is ok. Given that I'm on 4.2.2 already, will flashing the zip (which upgrades android from 4.4 to 4.4.2) even work? Doesn't that require the phone to be on 4.4?
Overall, I'm thinking of maybe not doing anything since the phone seems to work fine. I read that the cache is also not critically important to the OS and it only has logs, cache information and such.

Did you use twrp to wipe the cache?? Sometimes it takes a while. its a known bug
It happened to me... Just waited it out like 15 mins.. It went through
Sent from my Nexus 5

jdiddy_ub said:
Did you use twrp to wipe the cache?? Sometimes it takes a while. its a known bug
It happened to me... Just waited it out like 15 mins.. It went through
Sent from my Nexus 5
Click to expand...
Click to collapse
Nope. I did NOT have a Custom recovery. It was the Stock recovery. My phone was all stock except it was rooted and the bootloader was unlocked. I used CF-Auto Root for this.
I think what threw me off was how much time it took to clear Cache. Whatever device I've handled in the past, it takes 10 seconds to clear cache. With the Nexus 5, I boot into the bootloader (stock recovery), chose the recovery option and then Wipe Cache Partition. Nothing happens for 10 minutes except "Formatting Cache".
At this point, I grew impatient and thought something was wrong. Made the mistake of switching my phone off. And then all hell broke lose. I did not get a signal, no storage was recognized and nothing was accessible. Even factory Reset wasn't working from the bootloader. Every time I went to the bootloader it gave me errors on unable to mount cache, storage not accessible etc etc.
Flashing 4.4 stock image cache saved my life. I was thinking I bricked my phone for good. Won't be messing around with the Cache ever again.
Quick question: Can I do a nandroid backup with Stock recovery? I realize it's easy to do this with CWM or TWRP recoveries, but I have not installed them as yet. Thanks.

You can not do a nandroid with stock recovery

jd1639 said:
You can not do a nandroid with stock recovery
Click to expand...
Click to collapse
Wow. I didn't know that. That may be the single biggest reason to install a custom recovery.
The only reason I did NOT do CWM or TWRP was because I wanted to get OTA updates and be able to sideload them manually.
It seems with custom recoveries one has to flash to stock image every time an OTA comes. With Stock recovery I updated from 4.4 to 4.4.1 and 4.4.2 without any problems. I used adb to sideload the updates and then just used CF-AutoRoot to Reroot (my bootloader was unlocked). Very quick and painless.
Do you recommend installing a custom recovery to replace Stock?

[Q] Suggest a stable Rom which supports Xposed & GB. Further, I m using Lollipop 5.02

[Q] Suggest a stable Rom which supports Xposed & GB. Further, I m using Lollipop 5.02
Suggest a stable Rom for OnePlus One which supports Xposed & GB. Further, I m using Lollipop 5.02 Liquidsmooth and having bacon recovery. I want to know will I need to do a Factory reset and then wipe all the data or all just I need to use "Clear everything for New Rom?", the option available in Bacon recovery. This sounds a bit crazy, but my friend bricked its device so I want to be very careful because this seems a bit new to me, compared to the way Xiaomi Mi3 behaved.
Thanks a ton !

rizwan82 said:
Suggest a stable Rom for OnePlus One which supports Xposed & GB. Further, I m using Lollipop 5.02 Liquidsmooth and having bacon recovery. I want to know will I need to do a Factory reset and then wipe all the data or all just I need to use "Clear everything for New Rom?", the option available in Bacon recovery. This sounds a bit crazy, but my friend bricked its device so I want to be very careful because this seems a bit new to me, compared to the way Xiaomi Mi3 behaved.
Thanks a ton !
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rizwan82 said:
Suggest a stable Rom for OnePlus One which supports Xposed & GB. Further, I m using Lollipop 5.02 Liquidsmooth and having bacon recovery. I want to know will I need to do a Factory reset and then wipe all the data or all just I need to use "Clear everything for New Rom?", the option available in Bacon recovery. This sounds a bit crazy, but my friend bricked its device so I want to be very careful because this seems a bit new to me, compared to the way Xiaomi Mi3 behaved.
Thanks a ton !
Click to expand...
Click to collapse
Not really sure what you're saying in half of that post, but Xposed does not work with Lollipop so forget that idea.
What do u mean by GB?
Exactly which recovery are you using? Bacon is the codename for this device so all of the recoveries are for Bacon, but not named Bacon.
When flashing a new ROM you should wipe system, data, cache, and dalvik cache.
Transmitted via Bacon

GB = gravity box? If so you will need to stick with KitKat not any lollipop ROM. And since you're already on cm12 nightly the cm12 firmware is installed. That means you have to install cm11s firmware and modem first to get cm11s working again (probably how your friend messed up his phone).
There is a link in one of the cm12 custom ROM threads I can't remember which though. Search cm11s or cm11 firmware and you will probably find it.
Sent From Lollipopified Bacon Goodness!

ek69 said:
GB = gravity box? If so you will need to stick with KitKat not any lollipop ROM. And since you're already on cm12 nightly the cm12 firmware is installed. That means you have to install cm11s firmware and modem first to get cm11s working again (probably how your friend messed up his phone).
There is a link in one of the cm12 custom ROM threads I can't remember which though. Search cm11s or cm11 firmware and you will probably find it.
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
Thank u very much Timmaaa and ek69. Extremely sorry for not putting my question in a proper way. Let me do that now. Well, bacon was used by mistake, I m using Philz Touch 6.44.9 ClockworkMod v6.0.4.9 recovery in my phone.
In it, when we click on "Wipe Data/Factory Reset", there r 2 options namely"Wipe Data/Factory Reset" and "Clean to Install a New Rom". Now if I have a custom rom in my root directory, what M I supposed to click on ?? on "Wipe Data/Facory Reset" or "Clean to install a new rom".
Further, I also know that Xposed Installer & Gravity Box don't work on Lollipop. Even Viper4Android has also some issues on Lollipop. Therefore, I want to know a very stable rom which gives me the ultimate pleasure to use Xposed Installer & Gravity Box on my OnePlus One.
Thank you very much...

rizwan82 said:
Thank u very much Timmaaa and ek69. Extremely sorry for not putting my question in a proper way. Let me do that now. Well, bacon was used by mistake, I m using Philz Touch 6.44.9 ClockworkMod v6.0.4.9 recovery in my phone.
In it, when we click on "Wipe Data/Factory Reset", there r 2 options namely"Wipe Data/Factory Reset" and "Clean to Install a New Rom". Now if I have a custom rom in my root directory, what M I supposed to click on ?? on "Wipe Data/Facory Reset" or "Clean to install a new rom".
Further, I also know that Xposed Installer & Gravity Box don't work on Lollipop. Even Viper4Android has also some issues on Lollipop. Therefore, I want to know a very stable rom which gives me the ultimate pleasure to use Xposed Installer & Gravity Box on my OnePlus One.
Thank you very much...
Click to expand...
Click to collapse
I'm unfamiliar with Philz/CWM because I use TWRP because I believe it's a far superior recovery, so I don't quite know what each of those wipe options actually do. My guess is that the "clean to install new ROM" will wipe system, data, and your caches, so I'd use that option. But I'm only guessing.
It's too difficult to suggest one ROM over another, and I firmly believe it's disrespectful to the developers to do so. What I will suggest is for you to take a look at my index thread which lists all ROMs for this device (as well as all other important threads), that way you can have a look at what's on offer and decide for yourself.
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon

I can only recommend from my experience, liquid smooth has been..well smooth. So it gets my support, but if you're looking to mess around with things, lollipop might make that difficult as has been mentioned. I'm fairly sure exposed won't work at all. Your best option would be cm12 would it not?
Factory reset should also be fine.

Don't do factory reset in that recovery, I'm pretty sure I read somewhere that it will wipe the internal SD card as well. I guess do the other option to clean for a new ROM cuz that's the only one that is left lol. I also use TWRP so I can't guarantee anything. Or if you can manually wipe partitions then wipe the ones already written.
You have to stick with cm11s or some ROM based on cm11. I can't suggest any either since they all vary based on taste, features, etc. At this point they all are pretty much stable I would say. Also I agree with timmaaa you need to find one that works well for you. You have to read the first few posts of each ROM thread and see which one appeals to you
Sent From Lollipopified Bacon Goodness!

[Help Thread][Oneplus 7] Ask Any Question, Noob Friendly

This thread has been created
for
Questions & Answers/Troubleshooting
Specific to
Oneplus 7
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters​​@strongst​​​
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.​If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!​​Supporters: If you want to be put on or off the list, just make a request here in the thread!​Before posting anything, I strongly advise you to read​
XDA Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
​Specific Threads and Guides for Oneplus 7​
[GUIDE][OP7][9.0/10.0] Unlock Bootloader | TWRP | Root with Magisk | Update
Repository of Oneplus 7 Stock Roms(use in search function too)
Oneplus 7 TWRP Recovery
Oneplus 7 MSM Tool OxygenOS(Unbrick tool)
Oneplus 7 MSM Tool HydrogenOS(Unbrick tool)
Extract boot.img from Rom zip to get stock recovery and kernel
Feedback towards Oneplus over OP7 pro thread(builds are nearly identical)
OnePlus 7 & 7 Pro Cross Device Development
​​Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here. ​

Hello, I'm coming from several years of closed source Exynos Samsung. Struggle to get custom roms is a real pain. In addition, my love for bloatware, including big bro G apps/framework, is notoriously plunging to zero. So OP7 is gonna be my soon next phone.
Q: has anyone performed any deep clean of bloat and/or Google apps/framework on this model? Can it be done? In what %? Does it break anything natively working on OP7?
I know about the Tomatot, just what experience gives this process.
ps: I have a really bad OCD when reading com.google.abcdx
Nah, I'm good, just hate big brothers who spy on us.

w41ru5 said:
Hello, I'm coming from several years of closed source Exynos Samsung. Struggle to get custom roms is a real pain. In addition, my love for bloatware, including big bro G apps/framework, is notoriously plunging to zero. So OP7 is gonna be my soon next phone.
Q: has anyone performed any deep clean of bloat and/or Google apps/framework on this model? Can it be done? In what %? Does it break anything natively working on OP7?
I know about the Tomatot, just what experience gives this process.
ps: I have a really bad OCD when reading com.google.abcdx
Nah, I'm good, just hate big brothers who spy on us.
Click to expand...
Click to collapse
You can freeze/debloat nearly everything on OxygenOS without any impact compared to Samsung. I'm also debloat nearly everything from Google which comes pre-installed. But it's only minor compared to other OS.
Oneplus is one of the cleanest OS around and near to stock.

strongst said:
You can freeze/debloat nearly everything on OxygenOS without any impact compared to Samsung. I'm also debloat nearly everything from Google which comes pre-installed. But it's only minor compared to other OS.
Oneplus is one of the cleanest OS around and near to stock.
Click to expand...
Click to collapse
Right, thanks.
Steps: unlock bootloader, twrp, root Magisk, Tomatot, test.

w41ru5 said:
Right, thanks.
Steps: unlock bootloader, twrp, root Magisk, Tomatot, test.
Click to expand...
Click to collapse
Yeah, exactly. You can also have a look at xXx https://forum.xda-developers.com/on...agisk-rom-xxx-nolimits-7-0-speed-ram-t3933927 :good:

strongst said:
Yeah, exactly. You can also have a look at xXx https://forum.xda-developers.com/on...agisk-rom-xxx-nolimits-7-0-speed-ram-t3933927 :good:
Click to expand...
Click to collapse
Interesting concept. Thanks!

Hi guys. it would be good to add the two threads of MsmDownloadTool. The original that installs HydrogenOS and the other thread of a partner that puts OOS.
MsmDownloadTool HydrogenOS: https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
MsmDownloadTool OOS: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
---------- Post added at 04:57 PM ---------- Previous post was at 04:53 PM ----------
Another question, when using MsmDownloadTool you have to start the phone in EDL mode. This mode has a duration of 10 seconds, then the phone restarts. Any user who has used this tool can claim to restart in EDL mode after 10 seconds, but if you press Start, do you keep EDL mode by installing the ROM Stock?

Hello friends, I have a doubt, in other phones, when I wanted to put a clean ROM, even if it was the Stock, I always did it from TWRP:
1. Wipe / Advanced Wipe / and marked: Dalvik / ART Cache, System and Data.
2. Flash ROM OOS.
My questions are:
a) Has anyone tried to do that Wipe System? and can you confirm if you can then install the OOS ROM or cause problems and make brick ?.
b) Can you also do Wipe Vendor with Wipe System without causing brick?
Thank you and see if someone has done those steps and takes me out of doubt.

tURkOsANsE said:
Hello friends, I have a doubt, in other phones, when I wanted to put a clean ROM, even if it was the Stock, I always did it from TWRP:
1. Wipe / Advanced Wipe / and marked: Dalvik / ART Cache, System and Data.
2. Flash ROM OOS.
My questions are:
a) Has anyone tried to do that Wipe System? and can you confirm if you can then install the OOS ROM or cause problems and make brick ?.
b) Can you also do Wipe Vendor with Wipe System without causing brick?
Thank you and see if someone has done those steps and takes me out of doubt.
Click to expand...
Click to collapse
Why should you brick the phone when you wipe system /vendor and then flashing those partitions again when flashing OxygenOS?

strongst said:
Why should you brick the phone when you wipe system /vendor and then flashing those partitions again when flashing OxygenOS?
Click to expand...
Click to collapse
I have already read it several times in the forum, and they say that then you have to install ROM by fastboot. That's why I ask, in case a partner did it and it worked. when I updated on other ROM phones, instead of directly flashing the new ROM, first to wipe system and cache and then install the ROM update. to make a "semi-clean" installation. And now I don't know if it could be done by doing wipe system and vendor before installing.

Hello,
I ran into an issue today.
1- I downloaded the update through the phones updater. (9.5.8 BA. Full ZIP (2Go))
2- I went into TWRP and flashed latest twrp unofficial installer.
3- I flashed magisk
4- I rebooted into twrp, latest unofficial
5- Flashed OTA file from .OTA folder.
6- Flashed latest TWRP unofficial installer
7- Flashed magisk
=> stuck in bootloop.
Only fix was to go into twrp and manually select the other Slot, which worked thank god.
Anyone has a clue what I did wrong?

Nobody07 said:
Hello,
I ran into an issue today.
1- I downloaded the update through the phones updater. (9.5.8 BA. Full ZIP (2Go))
2- I went into TWRP and flashed latest twrp unofficial installer.
3- I flashed magisk
4- I rebooted into twrp, latest unofficial
5- Flashed OTA file from .OTA folder.
6- Flashed latest TWRP unofficial installer
7- Flashed magisk
=> stuck in bootloop.
Only fix was to go into twrp and manually select the other Slot, which worked thank god.
Anyone has a clue what I did wrong?
Click to expand...
Click to collapse
Hi guys, I put the steps I did to update when it is in OOS Stock with TWRP and Magisk, I did it from version 9.5.7 to 9.5.8 without problems, I do the method of installing everything in both slots, although there are people who only do it in a slot. I put what I did and it worked for me:
1. Backup with TWRP
2. Go to TWRP Reboot and see which slot you are in (then install it in the other slot).
3. In the first slot:
3.1. Go to Wipe Advanced and do Wipe Cache / Dalvik
3.2. OOS flashing
3.3. TWRP flashing
3.4. Flashing Magisk
4. Reboot TWRP
5. Change to second slot (go to Reboot and select the other slot:
5.1. Go to Wipe Advanced and do Wipe Cache / Dalvik
5.2. OOS flashing
5.3. TWRP flashing
5.4. Flashing Magisk
6. OPTIONAL: Change from Slot to the first (to go to Reboot and click on the other), I like to always work in the A, but that is a taste.
7. Reboot System.
PD: I use TWRP Blu_Spark:
https://github.com/engstk/android_device_oneplus_guacamole_unified_TWRP/releases/tag/v9.103
TWRP dev message: https://forum.xda-developers.com/showpost.php?p=79905872&postcount=29

tURkOsANsE said:
Hi guys, I put the steps I did to update when it is in OOS Stock with TWRP and Magisk, I did it from version 9.5.7 to 9.5.8 without problems, I do the method of installing everything in both slots, although there are people who only do it in a slot. I put what I did and it worked for me:
1. Backup with TWRP
2. Go to TWRP Reboot and see which slot you are in (then install it in the other slot).
3. In the first slot:
3.1. Go to Wipe Advanced and do Wipe Cache / Dalvik
3.2. OOS flashing
3.3. TWRP flashing
3.4. Flashing Magisk
4. Reboot TWRP
5. Change to second slot (go to Reboot and select the other slot:
5.1. Go to Wipe Advanced and do Wipe Cache / Dalvik
5.2. OOS flashing
5.3. TWRP flashing
5.4. Flashing Magisk
6. OPTIONAL: Change from Slot to the first (to go to Reboot and click on the other), I like to always work in the A, but that is a taste.
7. Reboot System.
PD: I use TWRP Blu_Spark:
https://github.com/engstk/android_device_oneplus_guacamole_unified_TWRP/releases/tag/v9.103
TWRP dev message: https://forum.xda-developers.com/showpost.php?p=79905872&postcount=29
Click to expand...
Click to collapse
Sooooo what you are saying is you flash on both slots so that both are ****ed if there is an issue?
Very smart.
With my issue I couldn't flash second slot anyway since I lose access to data.
Edit: Same issue with local update followed by twrp install through magisk.

Nobody07 said:
Sooooo what you are saying is you flash on both slots so that both are ****ed if there is an issue?
Very smart.
With my issue I couldn't flash second slot anyway since I lose access to data.
Edit: Same issue with local update followed by twrp install through magisk.
Click to expand...
Click to collapse
I put what I did and I had no problem. something you would do differently so that I don't let you install it:good:

Is there any news of pixel experience for oneplus 7??

Nobody07 said:
Sooooo what you are saying is you flash on both slots so that both are ****ed if there is an issue?
Very smart.
With my issue I couldn't flash second slot anyway since I lose access to data.
Edit: Same issue with local update followed by twrp install through magisk.
Click to expand...
Click to collapse
SO following on my issue, my suspicion is that there is something wrong on my slot A.
Slot B is where my current usable setup is. When installing an update it goes into slot A and it fails whatever I try.
My question would be, how can I copy my exact configuration of slot B to slot A, to try updating again?
Thank you !

Nobody07 said:
SO following on my issue, my suspicion is that there is something wrong on my slot A.
Slot B is where my current usable setup is. When installing an update it goes into slot A and it fails whatever I try.
My question would be, how can I copy my exact configuration of slot B to slot A, to try updating again?
Thank you !
Click to expand...
Click to collapse
Not sure what do you try there. Its much easier and safe to factory reset the whole phone and try to update it. Maybe you should also use MSMTool to go stock if nothing works.
Trust me it's a lot faster to backup your data and reset your phone before trying to copy slots.:good:

Kollachi said:
Not sure what do you try there. Its much easier and safe to factory reset the whole phone and try to update it. Maybe you should also use MSMTool to go stock if nothing works.
Trust me it's a lot faster to backup your data and reset your phone before trying to copy slots.:good:
Click to expand...
Click to collapse
I'm not going to share my whole life here, but that is not an option for now. I can't copy to my phone, and I can't install any tool on the computer I use.
Also it was stock before I flashed the actual 9.5.6. So chances are going back to stock would trigger the exact same thing. It had H2O on slot A when it arrived and OOS on slot B if I recall.
Whatever I am not able to do any of this right now, so copying over from slot B to A would be a good option if it was possible.

Nobody07 said:
I'm not going to share my whole life here, but that is not an option for now. I can't copy to my phone, and I can't install any tool on the computer I use.
Also it was stock before I flashed the actual 9.5.6. So chances are going back to stock would trigger the exact same thing. It had H2O on slot A when it arrived and OOS on slot B if I recall.
Whatever I am not able to do any of this right now, so copying over from slot B to A would be a good option if it was possible.
Click to expand...
Click to collapse
So you rather risk to lose all your data if you play with partitions and slots?
If there is no chance to backup data and reset the phone I wouldn't do anything for now. Hope you'll find a way to fix your problem.:good:

Kollachi said:
So you rather risk to lose all your data if you play with partitions and slots?
If there is no chance to backup data and reset the phone I wouldn't do anything for now. Hope you'll find a way to fix your problem.:good:
Click to expand...
Click to collapse
I guess I will just have to wait then.
What is your advice to be the more effective when it comes to backing up everything and putting it back again?
Can I just restore data + Internal storage + all the other partitions and it will be the exact same? If so should I first restore the data and then flash the ROM, or the other way around?
Thanks
Edit: Is there a possibility to only "reset" one slot?