Related
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?
I want to return to stock m8. I have the twrp back up and followed instructions putting it in to folder twrp-backup but when i boot into recovery the file folder isnt visable in the restore section. I can find the folder in the install section but without any executable files in. Im really stuck bin at this for hours. I followed the youtube video to the letter combining with the written instruction and cant understand where im going wrong. If it helps im on three uk. Any help would really be appriciated
Make sure the extracted backup folder is placed at TWRP/BACKUPS/YourDeviceSerialNo/FOLDER here
thanks for the quick reply, however the problem persists.
nothing is showing up in restore. when i rooted the handset i didnt install a custom rom just the custom recovery. now following the instructions for unroot i have to install a stock rom?? the version main on my m8 is 1.54.771.9 but the version of the stock im trying to install is 1.54.771.5 for three uk. i dont know if its because i have a stock rom onboard and the new one is an earlier version. if i dindnt install a custom rom why do i need to install a stock for unroot? cant i unroot using superuser then flash stock recovery then relock bootloader?
sorry its turned into a Q and A but i really dont understand
Can you make a backup with the TWRP recovery that you have now, only backup the boot.img. Then check in restore whether you can see it, if yes that's the place to put your full backup
From where that you got the 1.54.771.5 backup ? If it is from http://forum.xda-developers.com/showthread.php?t=2701376
this backup is for Philz recovery.
Oh yes your right but i was mistaken iv actually downloaded the twrp above it as its the only twrp avail for my cid this is the recovery iv tried but no luck. I will google how to make a back up of the twrp im running and give it a try. Is there no set default location the restore option would be looking for the recovery? Also in the stock rom i downloaded there are 9 entries inside but on the video tutorial his has more. xda is the only repo for these stock roms i can find so if its not a complete img then what do i do?
The location is as I mentioned above for TWRP.
I have no idea what video you're talking about.
I've seen many follow links outside of XDA but when they have problem, they come here .. I don't know why they can't get help from those outside links.
About the content of a TWRP backup, usually is 9 when there is no md5 created. In my nandroid backups that uploaded, there are only 8 files because I remove the recovery.log too.
And CWM or Philz recovery have about 14 or more
1anmu77ay said:
xda is the only repo for these stock roms i can find so if its not a complete img then what do i do?
Click to expand...
Click to collapse
Just google for outside links if you can find one that are not linked back to XDA.
For me, what we have on XDA is good enough.
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.
Wow, what a ride I had with this phone.
Starting with the fact that the model of the phone was SGH-I747 with AT&T branding I then tried to flash a custom ROM for this model, of course everything went bad, we'll not everything, but I couldn't make any calls, see IMEI nubmer and so on.
Thanks to a very helping member of SGH-I747 board, audit13, I found out that my phone is in fact T-Mobile's SHG-T999. I was lucky enough and was able to restore stock ROM of this model.
Now everything works, but since I'm located in Europe I would like to flash stock ROM without all the T-Mobile useless (since I don't have this carrier in my country) apps.
I found this ROM, which seems to be the one best used to get as close to stock android as possible - http://forum.xda-developers.com/showthread.php?t=2501303
And I just wanted to make sure that I don't miss anything important.
Phone Data
Model: SGH-T999
Bootloader version: T999UVUENC2
Android Version: 4.3
I've rooted the phone using this guide - http://forum.xda-developers.com/showthread.php?t=1771687 and using March 2014 - 4.3 JellyBean.
Could someone please explain difference between -StockMOD Custom ROM- and -StockMOD ROM-? I understand that -StockMOD ROM- is completely based on Stock ROM, little to no changes. But how little are these changes, will I have all the T-Mobile apps?
Steps I'm planning to make
1. Backing up efs folder by copying it with Root Browser to SD card and then on my PC.
2. Installing Clockwork MOD and Flashing ClockworkMod Recovery option
3. Creating backup of current ROM with ClockworkMod
4. Downloading StockMOD Custom ROM 4.3 RLS2.1.zip from the thread mentioned above (I'm a bit worried that file name in the thread is different - StockMOD Custom ROM T999 4.3 RLS2.1.zip)
5. Unfortunately I don't see link to T999UVUEMJC modem anywhere.
6. Copying of ROM file and Modem file to SD card (Is it ok if my SD card is only 2GB? ROM is a bit over 1GB).
7. Rebooting into recovery from ClockworkMod
8. Selecting Wipe data/factory reset
9. Selecting Wipe Cache partition
10. Going to advanced and selecting Wipe davlink cache
11. Selecting Mounts and Storage and format /system
12. Installing modem zip (If I can find it)
13. Installing StockMOD Custom ROM 4.3 RLS2.1.zip (is it ok to have spaces in file name?)
14. Praying to God everythings works
You could follow this thread to backup your efs folder: http://forum.xda-developers.com/showthread.php?t=1804117
I suggest flashing CWM directly from Odin in download mode. I would not install it using an App from the play store. This is just my personal preference.
All of the other steps look fine.
viltnieks said:
....Now everything works, but since I'm located in Europe I would like to flash stock ROM without all the T-Mobile useless (since I don't have this carrier in my country) apps.
I found this ROM, which seems to be the one best used to get as close to stock android as possible - http://forum.xda-developers.com/showthread.php?t=2501303
....
Could someone please explain difference between -StockMOD Custom ROM- and -StockMOD ROM-? I understand that -StockMOD ROM- is completely based on Stock ROM, little to no changes. But how little are these changes, will I have all the T-Mobile apps?
Click to expand...
Click to collapse
StockMOD Custom has much (if not all) of the carrier branding removed. It has added some customization tweaks to the ROM; mainly XPosed App and Wanam XPosed Module. It also has a few other custom apps and features from newer Galaxy devices replacing the stock apps. It is themed to look like a Galaxy S5 instead of an S3.
The StockMOD ROM has very little removed; KNOX, Syscope, CarrierIQ, and maybe something else. Other than that it will look almost identical to what you now have, including all of the T-Mobile stuff. This one would match the filename in the thread title. It was created first and the StockMOD Custom was added to the thread afterwards, is my guess.
Steps I'm planning to make
1. Backing up efs folder by copying it with Root Browser to SD card and then on my PC.
2. Installing Clockwork MOD and Flashing ClockworkMod Recovery option
3. Creating backup of current ROM with ClockworkMod
4. Downloading StockMOD Custom ROM 4.3 RLS2.1.zip from the thread mentioned above (I'm a bit worried that file name in the thread is different - StockMOD Custom ROM T999 4.3 RLS2.1.zip)
5. Unfortunately I don't see link to T999UVUEMJC modem anywhere.
6. Copying of ROM file and Modem file to SD card (Is it ok if my SD card is only 2GB? ROM is a bit over 1GB).
7. Rebooting into recovery from ClockworkMod
8. Selecting Wipe data/factory reset
9. Selecting Wipe Cache partition
10. Going to advanced and selecting Wipe davlink cache
11. Selecting Mounts and Storage and format /system
12. Installing modem zip (If I can find it)
13. Installing StockMOD Custom ROM 4.3 RLS2.1.zip (is it ok to have spaces in file name?)
14. Praying to God everythings works
Click to expand...
Click to collapse
I would also suggest this post for backing up imei and other nvdata. Specifically the reboot nvbackup instructions.
Since you are on NC2 bootloader and modem(baseband) do not mess with changing your modem to MJC (step 12). You can confirm that it will work on NC2 in the second line of the changelog of StockMOD Custom thread (post #2)
Another thing: I see StockMOD Custom has an Aroma Installer. I have not used a ROM with this option. Aroma Installer will give you choices during the ROM installation, I can only guess what they are without installing the ROM. The choices probably entail choosing between the stock apps and the later Galaxy device apps; Note 3, S4, and S5.
Thank you, I'm feeling a lot more confident now.
I will definitely check those links on backing up efs folders/IMEI.
viltnieks said:
Thank you, I'm feeling a lot more confident now.
I will definitely check those links on backing up efs folders/IMEI.
Click to expand...
Click to collapse
You're most welcome. I personally have used several of these methods, redundancy causes no harm.
dawgdoc said:
You're most welcome. I personally have used several of these methods, redundancy causes no harm.
Click to expand...
Click to collapse
I had hoped that everything would go smoothly from this point, it is nothing serious, but I have encountered a small problem.
I followed instruction in the link you provided Part B, point 4, I booted into recovery mode in order to install Synergy Backup. Installation starts, then I get this:
Preparing device...
Setting up 7z
Backing up EFS if unlocked
***Not unclocked Skipping Backup***
Install from sdcard complete.
What is really strange is that after going back and selecting reboot system I get this option in CWM:
Root access possibly lost. Fix?
-No
-Yes - Fix Root (/system/xbin/su)
I verified with titanium backup and root checker that I have root access.
viltnieks said:
I had hoped that everything would go smoothly from this point, it is nothing serious, but I have encountered a small problem.
I followed instruction in the link you provided Part B, point 4, I booted into recovery mode in order to install Synergy Backup. Installation starts, then I get this:
Preparing device...
Setting up 7z
Backing up EFS if unlocked
***Not unclocked Skipping Backup***
Install from sdcard complete.
What is really strange is that after going back and selecting reboot system I get this option in CWM:
Root access possibly lost. Fix?
-No
-Yes - Fix Root (/system/xbin/su)
I verified with titanium backup and root checker that I have root access.
Click to expand...
Click to collapse
Good news is that it caused no harm.
Confusing news is that that message was not caused by Part B, Point 4. I have seen that message before on my SGS3 but not my Captivate. On the SGS3 my custom recovery is TWRP not CWM. Also, I only did Part A, Point 2 on both devices. (The Captivate does have CWM as its recovery.) Fact is I have seen the message more than once, most of the time I selected the option to Fix. On the last time I selected No. I retained root on all occasions. I have seen others report seeing that message and I think it was from some action other than nvbackup. All this leaves me with no idea why it is happening.
dawgdoc said:
Good news is that it caused no harm.
Confusing news is that that message was not caused by Part B, Point 4. I have seen that message before on my SGS3 but not my Captivate. On the SGS3 my custom recovery is TWRP not CWM. Also, I only did Part A, Point 2 on both devices. (The Captivate does have CWM as its recovery.) Fact is I have seen the message more than once, most of the time I selected the option to Fix. On the last time I selected No. I retained root on all occasions. I have seen others report seeing that message and I think it was from some action other than nvbackup. All this leaves me with no idea why it is happening.
Click to expand...
Click to collapse
Coould it be related to the fact that I have data_1, data_2, data_3 folder in my root?
Also when I enter /storage/ I have a lot of folders like:
emulate
extSdCard
sdcard0
UsbDruveA
UsbDruveB
UsbDruveC
UsbDruveD
UsbDruveE
UsbDruveF
I guess this just isn't my lucky week.
I followed the steps mentioned above and install was successful, but I get no OS installed error.
Glad I made those backups...
EDIT:
For some reason the problem was with first file I downloaded in #2nd post StockMOD ROM named StockMOD Custom ROM T999 4.3 RLS2.1.zip
I then downloaded file from #3rd post StockMOD ROM named StockMOD ROM T999 4.3 v4.zip and was able to finish installation successfully. But as you said there is almost no change over the ROM I had before.
viltnieks said:
I guess this just isn't my lucky week.
I followed the steps mentioned above and install was successful, but I get no OS installed error.
Glad I made those backups...
EDIT:
For some reason the problem was with first file I downloaded in #2nd post StockMOD ROM named StockMOD Custom ROM T999 4.3 RLS2.1.zip
I then downloaded file from #3rd post StockMOD ROM named StockMOD ROM T999 4.3 v4.zip and was able to finish installation successfully. But as you said there is almost no change over the ROM I had before.
Click to expand...
Click to collapse
It's possible you had a bad download of the StockMOD Custom ROM. Did you verify the checksum after the download, assuming one was provided in post #2 or the download site? You could always download it again, without verifying, and see if it works correctly the second time.
I just checked my file system and /storage has all of the folders you named with an additional folder, /container. All of the /UsbDrive folders and /container are empty folders on my device. I do not have any idea where they came from.
dawgdoc said:
It's possible you had a bad download of the StockMOD Custom ROM. Did you verify the checksum after the download, assuming one was provided in post #2 or the download site? You could always download it again, without verifying, and see if it works correctly the second time.
I just checked my file system and /storage has all of the folders you named with an additional folder, /container. All of the /UsbDrive folders and /container are empty folders on my device. I do not have any idea where they came from.
Click to expand...
Click to collapse
As it turns out I needed to install StockMOD ROM T999 4.3 v4.zip which is the custom ROM and then update it with StockMOD Custom ROM T999 4.3 RLS2.1.zip
At least that's what I did, now everything works.
Thank you very much for sticking with me during this
There is one last thing that bothers me, during these last few days, I have installed, uninstalled apps, flashed roms, created backups, etc. There probably is a lot of "junk" on the phone at the moment. Is there a way to erase everything and just flash that custom ROM? Like when you reinstall Windows, you format disk and just install a fresh version of windows.
viltnieks said:
As it turns out I needed to install StockMOD ROM T999 4.3 v4.zip which is the custom ROM and then update it with StockMOD Custom ROM T999 4.3 RLS2.1.zip
At least that's what I did, now everything works.
Thank you very much for sticking with me during this
There is one last thing that bothers me, during these last few days, I have installed, uninstalled apps, flashed roms, created backups, etc. There probably is a lot of "junk" on the phone at the moment. Is there a way to erase everything and just flash that custom ROM? Like when you reinstall Windows, you format disk and just install a fresh version of windows.
Click to expand...
Click to collapse
Glad to hear you have been able to get the ROM you want loaded.
The way to clear out all of the detritus would be accomplished while in your custom recovery. In addition to wiping /cache and /dalvik-cache you would also format /data and /system before flashing the ROM. Before doing that, make sure you save anything you wish to reuse to your computer, or at least to an external micro SDcard. Stuff to be saved off the internal SDcard would include your backups, rom zips, and any app apks you may have a hard time finding again; not just music and pictures.
dawgdoc said:
Glad to hear you have been able to get the ROM you want loaded.
The way to clear out all of the detritus would be accomplished while in your custom recovery. In addition to wiping /cache and /dalvik-cache you would also format /data and /system before flashing the ROM. Before doing that, make sure you save anything you wish to reuse to your computer, or at least to an external micro SDcard. Stuff to be saved off the internal SDcard would include your backups, rom zips, and any app apks you may have a hard time finding again; not just music and pictures.
Click to expand...
Click to collapse
Thank you very much!