Hey as the title shows I want to know which firmware is the better one, to know I have TWRP installed so actually the better option would be the B513 repack for TWRP because otherwise I must install stock recovery and so on right? Is there a big difference between these two version? And which would you recommend?
Thanks in advance.
Which rom do you have installed currently?
digijedi007 said:
Which rom do you have installed currently?
Click to expand...
Click to collapse
Paranoid Android 4.45 the newest build.
Well in my opinion the actual stock software is better in this case than the custom ones, since in the b5x roms there are little to none bugs, I have used b510 now since it came out and i don't see the need to update again,everything works as it should (except the gps but then the gps in the p6 is horrible)so i'd say if you already have one of them use it, I actually prefer the stock based rom's because if something were to go seriously wrong I would still be able to send it in for repairs, and in my expierience the stock huawei roms work better than repacks, so my advice go for 132>B5x whatever you want they are all mostly the same except for very minor tweaks, easiest is b510, if you want some quick pointer's and a few must have mods try http://forum.xda-developers.com/showpost.php?p=54717666&postcount=8
Okay thanks man
Hey have you changed your rom yet? I would recommend you try this http://forum.xda-developers.com/ascend-p6/development/diy-rom-b510-based-add-want-t2843511, you can replace b510 with b511,b512,b513 if you wanted to
No not yet I am backing up my data right now, my plan was now to directly install B512 since its a full update.app and not a OTA like in the other firmwares. So now I install stock B510 recovery and boot.img and go straight to B512 and not install B132 before that should theoreticly work, or?
As far as i know you have to install b132 first otherwise it won't work(i think the b132 contains files that the b510,b512,b513 roms need(they are probly ota update files even if they look like normal firmware files) [note] did you download a repackged one? they might work like that.
---------- Post added at 12:15 PM ---------- Previous post was at 12:13 PM ----------
also fiy you could use titanium backup to make the process much much easier(hint of warning though don't restore alarms,bluetooth,wifi stuff between different android versions it will seriously mess up your phone)for call logs and messages use call logs backup & restore and for sms use sms backup and restore
http://www.huaweiblog.de/huawei/huawei-ascend-p6-firmwareupdate-b512-offiziell/ Here when you use google translator and scroll down they have the full firmware which can be flashed over all versions. For me that worked everytime with B506 and B507 which was kinda the same procedure. So I will try and report back if he doesn't update I will install B132 and so on
ok let me know what happens, i did see them mentioning the b132 firmware there near the bottom so maybe it's the same as the one's one the forum
So okay it worked without Problems I just installed boot.img and recovery.img from B510 and made a force update. Worked perfectly. Maybe you can add this to your thread.
so you extracted the boot .igm file and the recovery.img from the b510 and copied the 510's update.app file to the interal memory> flashed boot and rec > then flashed b510 > Is that how you did it? Keep in mind I need to keep the steps reasonably simple so that newbs to android(flashing etc) can also do it.
Okay
1. Starting with Paranoid Android, OMNI or any other AOSP-based ROM.
2. Backing up all data with Titanium backup and copy everything you need from your internal storage. ATTENTION: The internal storage will be wiped while flashing, so the backup MUST be on your SD-Card.
3. Copy dload folder to SD-Card or internal storage. (there should be no differnce)
4. Boot to TWRP and make a backup if something goes wrong.
5. In TWRP wipe everything except internal and external storage.
6. In TWRP choose reboot to bootloader. Confirm that no OS is installed and don't install SuperSU.
7. Plug your phone in your PC and open a CMD.
8. Download B510 recovery.img and boot.img from this thread http://forum.xda-developers.com/showthread.php?p=51718316 .
9. Follow the instructions by @surdu_petru. IMPORTANT: When the installation is finished and the phone reboots hold all three buttons and unplug the USB cable. (I needed more than one time to get it because the first time it was frozen in recovery. Just hold all three buttons till it reboots again.
10. You are finished!! The first boots takes some time no need to panic.
Additional:
Reinstall TWRP and flash SuperSU for Root. Than you can restore your backup you made in the second step.
Here you go. you can copy this in your post if you want.
Just one issue in your guide in step 9 you linked to his profile not the post
Oh yeah can you search for the right link I don't have time right now.
Edit: edited my first post.
Did you saw my correction?
Related
Hi guys,
I just picked up the One X international version and am loving every moment. So far, I've unlocked the bootloader from htcdev.com, installed the Clockwork mod recovery, made a backup, and installed SuperSU (in that order).
While waiting for the next version of ARHD to be released, I've got a few questions hopefully someone can help to answer
1) The directions say to manually flash the corresponding boot.img manually before flashing the ROM. Does this mean I do the reboot into fastboot and use the command prompt to type "fastboot boot boot.img"?
2) In the future when there are new versions of ARHD released, or I want to try a different ROM, do I just flash the new ROM over the existing one and that's it? Will all my settings and contacts still be intact on the phone or will it be erased? If it will be erased is there any way to back up just those info so I can restore on the updated ROM?
3) If/when I decide to sell the phone, is there a step by step guide somewhere I can follow to restore the phone back to factory conditions? I assume the backup I made of the phone after I installed Clockwork mod recovery will still be unlocked and have Clockwork installed?
Thanks in advance for any help/suggestions Can't wait to get started with the ROMs!
1) The directions say to manually flash the corresponding boot.img manually before flashing the ROM. Does this mean I do the reboot into fastboot and use the command prompt to type "fastboot boot boot.img"?
Yup that sounds about right to me.
2) In the future when there are new versions of ARHD released, or I want to try a different ROM, do I just flash the new ROM over the existing one and that's it? Will all my settings and contacts still be intact on the phone or will it be erased? If it will be erased is there any way to back up just those info so I can restore on the updated ROM?
If coming from ARHD I think you can just flash the new ROM directly onto the phone and you wont or shouldn't loose any data.
In the 'How to Flash' section of the ARHD Thread it reads:
Download "Super Wipe" script & place it on your SD card (optionally if coming from earlier version of my ROM, obligatory if coming from stock or other custom ROM) So basically, the Superwipe script wipes the whole phone, you do this when first flashing a ROM onto your phone, when flashing a newer version onto the phone it isn't necessary to perform a Superwipe.
3) If/when I decide to sell the phone, is there a step by step guide somewhere I can follow to restore the phone back to factory conditions? I assume the backup I made of the phone after I installed Clockwork mod recovery will still be unlocked and have Clockwork installed?
There are guides somewhere, I'll look for them and PM you a link if I can find it, however a lot of people sell their phones rooted and with custom roms on nowadays. Only re-locking them if they're trying to gain back some warranty.
---Edit---
This is a good thread to read through: http://forum.xda-developers.com/showthread.php?t=1799881&highlight=unrooting
A guide to unrooting: http://onexroot.com/category/one-x-unroot/
And here are the shipped RUUs for the Endeavour: http://forum.xda-developers.com/showpost.php?p=23542734&postcount=1
The-Last-Hylian said:
1) The directions say to manually flash the corresponding boot.img manually before flashing the ROM. Does this mean I do the reboot into fastboot and use the command prompt to type "fastboot boot boot.img"?
Yup that sounds about right to me.
2) In the future when there are new versions of ARHD released, or I want to try a different ROM, do I just flash the new ROM over the existing one and that's it? Will all my settings and contacts still be intact on the phone or will it be erased? If it will be erased is there any way to back up just those info so I can restore on the updated ROM?
If coming from ARHD I think you can just flash the new ROM directly onto the phone and you wont or shouldn't loose any data.
In the 'How to Flash' section of the ARHD Thread it reads:
Download "Super Wipe" script & place it on your SD card (optionally if coming from earlier version of my ROM, obligatory if coming from stock or other custom ROM) So basically, the Superwipe script wipes the whole phone, you do this when first flashing a ROM onto your phone, when flashing a newer version onto the phone it isn't necessary to perform a Superwipe.
3) If/when I decide to sell the phone, is there a step by step guide somewhere I can follow to restore the phone back to factory conditions? I assume the backup I made of the phone after I installed Clockwork mod recovery will still be unlocked and have Clockwork installed?
There are guides somewhere, I'll look for them and PM you a link if I can find it, however a lot of people sell their phones rooted and with custom roms on nowadays. Only re-locking them if they're trying to gain back some warranty.
---Edit---
This is a good thread to read through: http://forum.xda-developers.com/showthread.php?t=1799881&highlight=unrooting
A guide to unrooting: http://onexroot.com/category/one-x-unroot/
And here are the shipped RUUs for the Endeavour: http://forum.xda-developers.com/showpost.php?p=23542734&postcount=1
Click to expand...
Click to collapse
Awesome, thanks for the reply and links! I have one last question hopefully someone can confirm... I assume once I flash to any custom ROM whenever there is a software update on the phone I should NOT update? Is it safe to update the apps through the Google Play store such as Facebook GMail etc?
Well with venom Rom for hox u can update it is actually the only rom that has over the air updates directly by the people that made the rom also most customizable Rom too.
Sent from my HTC One X using xda app-developers app
HungryPillow said:
Awesome, thanks for the reply and links! I have one last question hopefully someone can confirm... I assume once I flash to any custom ROM whenever there is a software update on the phone I should NOT update? Is it safe to update the apps through the Google Play store such as Facebook GMail etc?
Click to expand...
Click to collapse
It's safe to update any Apps and things through the Play Store yeah, On a lot of ROMs the OTA Updater is disabled, you'll have to flash the latest RUU onto the phone to get the Update.
E.G We had an ARHD ROM that was running off the 1.29.401.11 update, now we've got a version of ARHD that's running off 2.05.401.2 instead as Mike had updated the ROM to include the latest updates, so everytime there is a new update, the ROMs get updated by the Devs and we can reflash on said ROM.
HungryPillow said:
Awesome, thanks for the reply and links! I have one last question hopefully someone can confirm... I assume once I flash to any custom ROM whenever there is a software update on the phone I should NOT update? Is it safe to update the apps through the Google Play store such as Facebook GMail etc?
Click to expand...
Click to collapse
You may safly update anything from Market (Play). You may backup your phonebook in Google account and through settings in phone book (Export to SD or somthing like this). SMS you may backup also to SD card or to email (there is an option in it). Or try ROMcleaner 2.1 it will backup some settings also and user apps.
And when Mike (ARHD developer) release new ROM, if it is based on NEW official update (RUU) with new sw version it is highly recomended to do a full wipe(Super Wipe script is in his thread). It will erase every app and configuration, except you SD card files.
The correct command is fastboot flash boot boot.img, not fastboot boot boot.img
Sent from my HOX running CMX by Tbalden.
Hi all!
Sorry for posting a new thread about this, but I'm really confused about what should I do.
I'm currently on P6-U06V100R001C00B111 - rooted, and I would like to use KitKat stock or custom, doesn't matter. Can I just put ROM files on SD and go on "Local update" in settings? Or do I have to install ADB and fastboot as described here
Any help would be greatly appreciated. Thanks.
soul_train said:
Hi all!
Sorry for posting a new thread about this, but I'm really confused about what should I do.
I'm currently on P6-U06V100R001C00B111 - rooted, and I would like to use KitKat stock or custom, doesn't matter. Can I just put ROM files on SD and go on "Local update" in settings? Or do I have to install ADB and fastboot as described here
Any help would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
First of all, wrong forum..
Second I belive there are many ways of doin this update.
This is what I did:
1. Placed the update.app on a Sdcard and did a locale-update by going into settings
2. The phone will reboot and the update will start.
3. You are know on KK, but you will not have a working PlayStore since the old one is for JB.
Basicly this is what u need to do to be on KK, but if you want Playstore etc you have to install TWRP and flash gapps, and if I remember right you need to flash TWRP via fastboot.
I wanted a clean install so after I had installed TWRP I did a factory reset and wiped the internal memory and installed KK (.zip-file) and Gapps via TWRP from my Sdcard.
This is how I did and maybe someone else can tell u a better way to do it.
Can anyone post the link for what rom can i flash?
Fancy Pants said:
First of all, wrong forum..
Second I belive there are many ways of doin this update.
This is what I did:
1. Placed the update.app on a Sdcard and did a locale-update by going into settings
2. The phone will reboot and the update will start.
3. You are know on KK, but you will not have a working PlayStore since the old one is for JB.
Basicly this is what u need to do to be on KK, but if you want Playstore etc you have to install TWRP and flash gapps, and if I remember right you need to flash TWRP via fastboot.
I wanted a clean install so after I had installed TWRP I did a factory reset and wiped the internal memory and installed KK (.zip-file) and Gapps via TWRP from my Sdcard.
This is how I did and maybe someone else can tell u a better way to do it.
Click to expand...
Click to collapse
I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!
AndroidUzer said:
I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!
Click to expand...
Click to collapse
Wondering same thing. How to get update, the reroot without having to do a full return to stock first.
Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.
It worked!
Swizzle82 said:
Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.
Click to expand...
Click to collapse
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.
AndroidUzer said:
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.
Click to expand...
Click to collapse
Hey, I've been searching through the forums trying to find the stock recovery/boot images for the last hour to no avail. Would it be possible for you to post links to where you found them? Thanks!
EDIT: Annnnnnnnnnd of course as soon as I ask, I find it in another thread I was reading http://forum.xda-developers.com/showpost.php?p=55359856&postcount=125
Where can i found the stock boot.image and stock recovery.img
bjg020683 said:
Where can i found the stock boot.image and stock recovery.img
Click to expand...
Click to collapse
Link in post just above yours...
Thanks
Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!
laoh said:
Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!
Click to expand...
Click to collapse
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!
AndroidUzer said:
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!
Click to expand...
Click to collapse
Thanks for the lengthy explanation. Can I verify if what I'm trying to do is same as what you've done? Here's my situation.
- I have the stock LG 4.4.2 KK rom for D851. Not stock AOSP or CM or any other "custom ROM".
- It is rooted and have TWRP
- The only thing I've really done to the rom is to debloat - used Titanium to freeze lots of apps that came with the LG rom. I have not deleted any since I've read before that if you delete them, it will make it a pain to upgrade to newer Android versions.
So I've learned the hard way trying to update my phone from 4.4.2 to 5.0.1 LG rom.
- I took the OTA and tried to install it. Big mistake. I ended up in a TWRP bootloop. Had me cringing thinking I just lost everything until I found this post http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508 and fixed it with LG_G3_Flash2FixStuckRecovery.zip (flashed it with TWRP). What a godsend it was. Got me out of bootloop and I didn't have to do factory reset or anything. All my apps and data are intact just the way it was before I began OTA.
- So now I'm back to where I started originally before attempting to OTA to Lollipop.
If I'm reading correctly, what I need to do are:
- Unfreeze all apps
- Restore stock recovery (recovery.img) and boot file (boot.img) - this essentially reverses root and custom recovery. Use Flashify to do so.
- Flash the stock LG Lollipop update (btw - the phone says that the new ROM is already downloaded and ready to go but there's nothing in the cache folder... is there somewhere else I should be looking?)
- Before I reboot - I should flash SuperSU and TWRP which restores root and custom recovery
- Reboot phone, cross fingers.
Somewhere in the middle, am I reading that you need to restore LG stock Kitkat rom first (which I already am on), then update to Lollipop? I'm reading that from this part "This will allow you to go straight to "r" skipping "m" all together. If you are feeling brave and competent you could go straight to Lollipop..."
I'm confused here...
One last thing - Once I'm upgradded to Lollipop, is there an easy way to freeze all the apps I had frozen before instead of going one by one? I have the paid Titanium version but I can't figure out if it has a batch/mass freeze feature.
Thanks!!
No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!
AndroidUzer said:
No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!
Click to expand...
Click to collapse
I appreciate all of your advice. The thing is, I'm trying to upgrade to Lollipop... I'm already on Kitkat and not really interested in upgrading to a latter dot version of Kitkat.... It just seems like a difficult proposition to do OTA upgrade if you rooted and have non-stock recovery. Since I'm on tmobile d851 stock Kitkat (rooted with frozen apps), I should've never put put TWRP. I thought I might put custom ROM on it but never got around to it and since you pretty much lose wifi calling with non-Tmobile ROMs, I just never did... More of a pain now....
Hey guys
I am completely new in this topic. I just got an Samsung Galaxy Tab S (SMT700 Wifi) as a present a few days ago. Its my first android device I had so far.... so everyone will call me "noob" and I am okay with it DD
When I realised that there are different android os development projects like CM and Paranoid, I become interested in trying them out. so...
1.) Is it possible to brick the android device completely or is there something like an recovery/dfu mode in iOS devices?
2.) Can I go back to the stock OS contributed bey samsung itself (Touchwiz Kitkat)? If yes are this files online?
3.) Does I need special hardware to perform a custom rom flash? (micros card/special OS on pc (linux,....)
4.) Does the CM blck mod in the official forums contains alle required drivers and blobs already to perform gpu tasks and so on? (are there currently downsides swell?)
Thx :fingers-crossed:
androidnoob222 said:
Hey guys
I am completely new in this topic. I just got an Samsung Galaxy Tab S (SMT700 Wifi) as a present a few days ago. Its my first android device I had so far.... so everyone will call me "noob" and I am okay with it DD
When I realised that there are different android os development projects like CM and Paranoid, I become interested in trying them out. so...
1.) Is it possible to brick the android device completely or is there something like an recovery/dfu mode in iOS devices?
2.) Can I go back to the stock OS contributed bey samsung itself (Touchwiz Kitkat)? If yes are this files online?
3.) Does I need special hardware to perform a custom rom flash? (micros card/special OS on pc (linux,....)
4.) Does the CM blck mod in the official forums contains alle required drivers and blobs already to perform gpu tasks and so on? (are there currently downsides swell?)
Thx :fingers-crossed:
Click to expand...
Click to collapse
1. There is bootloops but hardbricks are rare. You can enter recovery and download mode(flash stock rom on broke os) in a bootloop. Just hold power, home or vol up for recovery and home +power +vol down for download mode.
2. Yes you can go back to any version of stock os unlike apple you have to be on the latest. The files are online for your device at sammobile. (google it) and also samsung updates.
3. All you need to perform a custom rom flash is a custom recovery called twrp and your device. Theres an app on google play for installation of it. (search on youtube on how to do so). But thats just flashing zip based roms(which most custom roms are). For stock rom installation, you will need a pc and a application called odin 309 to flash a stock md5 file rom in which you will need to be in download mode (like installing new update from itunes).
You will need to backup your whole rom with twrp before flashing a custom rom. You may need a micro sd if your short on space. You will also need to be rooted to install custom roms. Please go to the cfautoroot thread of your device to root your device in which you will viod warrenty.
4. Cm rom as of now still has bugs but is still useable for games and such. There should be a list of bugs on the thread and might have some missing features such as ir blaster and finger print scanner. Battery life may vary. So there are downsides.
5. I can go into more depth of custom stuff and flashing if you wish. Right now my fingers hurts xD. Hope this helps!
1) it is very, very unlikely even if you try intentionally to do so
2) yes, no problem. google for Samsung Firwares, it's all online
3) windows PC, Odin Software, and an USB cable, that's all. You can do it with Linux if you prefer. Some Roms are installed via zip file from the device itself, then you need to flash a new Recovery partition first, that is able to do so
4) ?
Thx you very much for the help !
After reading a lot about this topic it seems to be not as difficult as I thought it would be.
But I don't get one thing. Why does I need to make a proper backup only for the flashing propos? If I flash my internal memory, all data will be replaced. And if it goes wrong I will be able to do a complet software reset with odin and the original samsung image found in the Internet?! So why I have to make a backup (there is no data in my current tap I will need in the future)?
And does the cf chain root flash the OS or the firmware ?
As my understanding tell me that the firmware is something comparable to a bios , which should never be flashed to maintain stability.
So as my logic goes further if my device is rooted, after a proper reset it will not be rooted anymore? (Android stock reset function in settings)
Or does armbased devices not have a normal firmware/bios as I mentioned ? And something in the bootprocess itself is manipulated to anable root access?
Hopefully you get what i mean :angel:
androidnoob222 said:
Thx you very much for the help !
After reading a lot about this topic it seems to be not as difficult as I thought it would be.
But I don't get one thing. Why does I need to make a proper backup only for the flashing propos? If I flash my internal memory, all data will be replaced. And if it goes wrong I will be able to do a complet software reset with odin and the original samsung image found in the Internet?! So why I have to make a backup (there is no data in my current tap I will need in the future)?
And does the cf chain root flash the OS or the firmware ?
As my understanding tell me that the firmware is something comparable to a bios , which should never be flashed to maintain stability.
So as my logic goes further if my device is rooted, after a proper reset it will not be rooted anymore? (Android stock reset function in settings)
Or does armbased devices not have a normal firmware/bios as I mentioned ? And something in the bootprocess itself is manipulated to anable root access?
Hopefully you get what i mean :angel:
Click to expand...
Click to collapse
1. Sometimes odin and kies will fail for you. Twrp backups is to be really safe if you get bootlooped and odin fails for you. Its much easyer to restore a twrp backup and easy to make one. Its just if odin or kies fails which twrpnwould be your only hope. Just in case
2. Cfautoroot only flashes supersu and root. It keeps your apps and everything. So when you flash cfautoroot, it will say andriod is upgrading becuase its installing root and restoring back your apps.
3. After a full proper reset, it will not have root and revert back to stock. Thats where you flash cfautoroot to gain root again!
Hope this helps!
So as of now I managed to root my device and also created a twrc backup, which is now transfered to my sd card
Are there major differences between a rom flash with twrc recovery or odin?
androidnoob222 said:
So as of now I managed to root my device and also created a twrc backup, which is now transfered to my sd card
Are there major differences between a rom flash with twrc recovery or odin?
Click to expand...
Click to collapse
Most custom roms are to be flashed with twrp. Meanwhile stock roms/md5 is to be flashed with odin(firmware from website).
Again Thx you very much!! You are awesome!
I managed to install cyanogenmod its insanely fast compared to the touchwiz version
But there is one more thing I have to ask.
I installed TWR in the latest version but the klimwifi (2.8.XX) version (klimtwifixx was not avaible). Is this the right version?
Where exactly does TWR be installed. Afther the wipe and the format it stays, so I have no clue how it can be available even if the internel memory was formated?
I started TWR by the terminal (reboot recovery), becouse I have no clue how to start it instead by button pressing?
And there are no playstore how can i get it on cm11?
androidnoob222 said:
Again Thx you very much!! You are awesome!
I managed to install cyanogenmod its insanely fast compared to the touchwiz version
But there is one more thing I have to ask.
I installed TWR in the latest version but the klimwifi (2.8.XX) version (klimtwifixx was not avaible). Is this the right version?
Where exactly does TWR be installed. Afther the wipe and the format it stays, so I have no clue how it can be available even if the internel memory was formated?
I started TWR by the terminal (reboot recovery), becouse I have no clue how to start it instead by button pressing?
And there are no playstore how can i get it on cm11?
Click to expand...
Click to collapse
2.8 is the latest version of twrp. I dont think your device is klimwifixx. It should be klimwifi. What the wipe and and factory reset in twrp does is that it clears all your apps and wipe cache. It does not wipe any folders and it justs wipes your apps. So internal should not be affected unless you formatted it... You just need to swipe the factory reset on it when installing roms. For google play store you have to flash a file name gapps. There should be a link to it on the thread. To get into recovery, turn off your device, then hold power, home, vol up buttons at the same time to enter recovery. To exit recover just touch the reboot rectangle and hit reboot system. Hope this helps!
Okay now its clear TWRP replace the "downloade mode", which is the standard recoverymode
You said I do not need to format the disk, but why?
In linux distributions (debian for example) you will have similliar structure for example /var /bin /sbin /usr /proc,.....
If there is the stock touchwiz android it will have this structure listed above as well. So it will courrupt the os by overwriting this folders by a custom rom....
. Maybe you wont do it in the TWRP menue, because it will do it automatically by choose you custom rom install script in the zip?
How is the portioning in those devices? Maybe there are /dev/sda1 (android) and /dev/sda2 (with the recovery setup inside)....? I just want to understand those things
androidnoob222 said:
Okay now its clear TWRP replace the "downloade mode", which is the standard recoverymode
You said I do not need to format the disk, but why?
In linux distributions (debian for example) you will have similliar structure for example /var /bin /sbin /usr /proc,.....
If there is the stock touchwiz android it will have this structure listed above as well. So it will courrupt the os by overwriting this folders by a custom rom....
. Maybe you wont do it in the TWRP menue, because it will do it automatically by choose you custom rom install script in the zip?
How is the portioning in those devices? Maybe there are /dev/sda1 (android) and /dev/sda2 (with the recovery setup inside)....? I just want to understand those things
Click to expand...
Click to collapse
No no! Twrp replaces stock recovery. Download mode cannot be replaced. You enter it by holding power, vol down, home button when the device is off. Download mode is when you flash things. Recovery mode is when you clear cache or other stuffs. I have no idea with the linux stuff you explained but custom zip roms just adds some modifications and other stuff to the device. You would need to clear cache and factory reset so you wont have problems installing it. You can easyly go back to stock rooted by restoreing a backup you made in twrp. It has to do something with img and replacing those if thats what your talking about idk. No need to format as the rom add things to it. Just need to factory reset and cleae caches.
But now if I want to enter download mode for testing, it will boot into the twrp recovery. So as for me it looks like that it is already replaced..
androidnoob222 said:
But now if I want to enter download mode for testing, it will boot into the twrp recovery. So as for me it looks like that it is already replaced..
Click to expand...
Click to collapse
It shouldnt be as twrp only replaces recovery. Img did you try doing home, power, vol down?
Hi
I have a quick question I have the Galaxy tab S 10.5 wifi and was wondering can I install TWRP without the tablet being rooted?
Also there are some builds where it states that its rooted, debloated and de-knocked. Does this mean that they can be flashed without rooting the tablet and tripping knox.
Thanks for your replies, still trying to get my head around this.
I've made a TWRP backup of my system if anyone wants to try it.
It's the TW ROM, updated to MM. Made with TWRP 3.
It's a self extracting ZIP file so download to a folder on your computer before continuing.
I don't know if it'll install over the JP ROM but you're welcome to try if you like.
ADVISORY......
MAKE A BACKUP OF YOUR ROM FIRST BECAUSE I HAVE NO IDEA IF THIS WILL WORK!!
OK. Boot into TWRP and make a backup of your entire ROM.
Boot the phone to Android and connect to the computer so as you can navigate through the storage.
Using the computer, find the TWRP folder on the phone and find the last folder. It'll be called something like "Internal storage\TWRP\BACKUPS\<HT57DYW00000>" (where HT57DYW00000 is a folder with YOUR serial number as it's name).
Copy the folder you extracted into this folder, alongside your own backup.
Then, reboot into RECOVERY and select RESTORE.
Choose the SYSTEM backup you copied into your folder BUT ONLY IF YOU MADE A BACKUP OF YOUR ROM!
Wipe the CACHE and DALVIK CACHE and reboot.
Like I said, I don't know if it'll overwrite the JP ROM or if it'll work at all but if you want to try it you're welcome to.
Download from here:
https://drive.google.com/open?id=0B01V_alsJMzLcVNabjcyMXNRcm8
Incidentally, this was born of a failed attempt to make a system image using TWRP which failed a few times. Anyone managed to do this? or is it a fault with TWRP?
I think, we start porting applications from Taiwan rom stock 5.0.1 to JP romstock.
After B3 HTV31 update android 6.0, We re-started porting applications from HTC 10 rom stock to B3 JP romstock
https://www.facebook.com/BOAROM/posts/1083701208319409
Would it be safe to use this recovery from TWRP v2.8.7 or should I update to TWRP 3 first?
EDIT: Nevermind, I'll try with TWRP 3.
Well, from a KDDI stock it goes straight to the bootloader, and whatever reboot you do will take you there.
My guess is you'd have to change the CID too, at least.
ToTTenTranz said:
Well, from a KDDI stock it goes straight to the bootloader, and whatever reboot you do will take you there.
My guess is you'd have to change the CID too, at least.
Click to expand...
Click to collapse
Possibly, yeah. I wiped mine and restored it from that without any problems but I'm super CID'd so that'd work too I guess.
mrquyen1993 said:
I think, we start porting applications from Taiwan rom stock 5.0.1 to JP romstock.
After B3 HTV31 update android 6.0, We re-started porting applications from HTC 10 rom stock to B3 JP romstock
https://www.facebook.com/BOAROM/posts/1083701208319409
Click to expand...
Click to collapse
I've been using the camera from the 10 but there's not a lot of point. It doesn't really add anything to the stock camera other than looking different.
We're on the list for the JP update:
http://www.au.kddi.com/information/topic/mobile/20160304-01.html
but it hasn't been issued yet:
http://www.au.kddi.com/information/notice_mobile/update/list/