Related
Hi XDA Community!
I can find information to about almost single topic, but the big problem is, i dont know where exactly to start with and the correct order of all of these steps.
What i wanna do is, like on a pc, format the whole phone, delete everything and set up a custom rom and root the phone.
My first step was trying to root it because i dont know if the root is related to the OS or to the phone kernel.....
I tried the CF-Autoroot procedure from XDA-Forum http://forum.xda-developers.com/showthread.php?t=2219803 but i experience the same issue as many other users. When i click start the process starts, but gets stuck immediately when it comes to the imaging step. Then i get no response from my phone or Odin anymore, the bar wont process for hours.
I tried different USB ports, same result. But i can exchange data from phone OS to pc via USB without problems !
So im kind of thrown back now and i dont know what to do or where to start. Can anyone help me ?
5 Years ago i cooked a rom for my Sony Xperia X1 and put it on my phone without any problems lol, and now with Samsung i get only problems.....
If you want to put a custom ROM on it you only need to flash a custom recovery.
This can be done, also, with Odin.
The only other steps are with ADB or root.
TWRP have install instructions (for all methods) on their site.
One important thing is that you also have to take your device model into consideration. Some models (AT&T & Verizon) have locked bootloaders, which make the whole process of rooting and flashing a pain in the butt.
GDReaper said:
If you want to put a custom ROM on it you only need to flash a custom recovery.
This can be done, also, with Odin.
The only other steps are with ADB or root.
TWRP have install instructions (for all methods) on their site.
One important thing is that you also have to take your device model into consideration. Some models (AT&T & Verizon) have locked bootloaders, which make the whole process of rooting and flashing a pain in the butt.
Click to expand...
Click to collapse
My phone is NOT locked. But my question was the correct ORDER of these things to do. Please read my question carefully. What I do first and what comes next ? I also want to root my phone for full acess
C128D said:
My phone is NOT locked. But my question was the correct ORDER of these things to do. Please read my question carefully. What I do first and what comes next ? I also want to root my phone for full acess
Click to expand...
Click to collapse
I read it and I told you.
If you want to put a custom ROM on it, you have to flash a custom recovery First!
Recovery and root are two independent things. The only reason to root first would be if you want to backup your apps and data of your current ROM.
Custom ROMs are pre-rooted
Otherwise flash a custom recovery, put the ROM zip on your microSD card, boot into recovery, wipe the phone, flash the ROM.
And don't forget about gapps.
Since you said you've already flashed ROMs before, this shouldn't be anything different from what you did before.
Well, it was a lot easier on my Sony, even cooking the rom was a first time success. Here im struggling really hard since i feel im running around in circles, not able to proceed...
First of all some details to my phone:
Android 5.0.1
API Level 21
Bootloader I9505XXUHOJ2
Build ID LRX22C.I9505XXUHOJ2
Java VM ART 2.1.0
OpenGL ES 3.0
Kernel armv7l
Kernel V 3.4.0-5978264 (I9505XXUHOJ2)
Root No
Thing is, every source tells me that I need TWRP or a different custom loader to flash the ROM. But i cannot install it since my phone isnt rooted and the ODIN root-method fails for me, since the process stops right in the beginning at the recovery.img, like its hung up. I tried everything from different USB ports to disabling windows firewall and enabling USBdebugging in the developer settings of my phone... Still same result, no sucess....
Is there any way to do this via Kies ? What should I do ?
C128D said:
Well, it was a lot easier on my Sony, even cooking the rom was a first time success. Here im struggling really hard since i feel im running around in circles, not able to proceed...
First of all some details to my phone:
Android 5.0.1
API Level 21
Bootloader I9505XXUHOJ2
Build ID LRX22C.I9505XXUHOJ2
Java VM ART 2.1.0
OpenGL ES 3.0
Kernel armv7l
Kernel V 3.4.0-5978264 (I9505XXUHOJ2)
Root No
Thing is, every source tells me that I need TWRP or a different custom loader to flash the ROM. But i cannot install it since my phone isnt rooted and the ODIN root-method fails for me, since the process stops right in the beginning at the recovery.img, like its hung up. I tried everything from different USB ports to disabling windows firewall and enabling USBdebugging in the developer settings of my phone... Still same result, no sucess....
Is there any way to do this via Kies ? What should I do ?
Click to expand...
Click to collapse
There are 3 methods to flash TWRP:
1) Root and Flashify
2) Odin
3) ADB
Since rooting with Odin doesn't work, maybe you should try flashing recovery with Odin.
Have you tried a different version of Odin or a different Windows version?
CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs
I flashed this but I didn't get the custom boot logo.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine
Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo
mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0
Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.
The app downloaded from f-droid worked for me as well, many thanks!
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.
Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.
I can't seem to figure out how to downgrade back to a stock ROM after installing this:
lineage-14.1-20170331-UNOFFICIAL-trltetmo.zip (can't post link yet)
I believe it's the Nougat 7.1.1
I want to downgrade to 6.0.1 or 5.1.1
One message I see is "Recovery is not Seandroid Enforcing". Seems like all fixes suggest reinstalling stock ROM, which I'm trying to do, but can't.
Phone is a Samsung Note 4 SM-N910W8 (Rogers)
What's your steps to downgrade to 6.0.1? Did you download Rogers ROM and ODIN it(google is your best friend)?
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
If ODIN starts and stops immediately, you have a different problem. Did you install the Samsung Android USB driver properly. Anyway, you have a software issue, fix it first. I suggest you watch a few related video on youtube.
ziggy1971 said:
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
Click to expand...
Click to collapse
Currently no response.
In the freezer... I'm waiting.
Not sure which I should follow first:
Debrick here: https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
or
The following from https://forum.xda-developers.com/showpost.php?p=72338162&postcount=2622
SUREFACE said:
It Sounds that You have a "FULL BRICK" !
The Only way, that REALY can Help is a "USB-JIG".
And Hope, that this One Brings Your Device back in Download-Mode!
You can Build Your Own One, see here : https://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707
Or Buy One! See Here: https://www.amazon.de/Download-Repair-Stecker-Samsung-Galaxy/dp/B004VN5ZYS
And You need a REPAIR ROM ! Take A Look here for Your Variant : https://mega.nz/#F!Ax0gxSzZ!Qq_eJWX678bQHBhn7BHNDQ
Hope that this will Work!
Click to expand...
Click to collapse
Since yesterday I did the following:
- reset my system with a backup image (Bare Metal Restore with True Image) I only have some basic software installed.
- downloaded and installed SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0
Is your phone booting up and functioning? If it is, why are you talking about debrick? I'm assuming that you're "new" to all this. I suggest you read up(especially the stickies) and be comfortable before you go further.
ziggy1971 said:
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
Click to expand...
Click to collapse
ziggy1971 said:
Not sure which I should follow first:
Debrick here: https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
or
The following from https://forum.xda-developers.com/showpost.php?p=72338162&postcount=2622
Since yesterday I did the following:
- reset my system with a backup image (Bare Metal Restore with True Image) I only have some basic software installed.
- downloaded and installed SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0
Click to expand...
Click to collapse
No, it doesn't boot up at all now.
I know I initially said "I" installed the custom ROM, I didn't, I bought it that way. The previous owner won't do anything to help. The only thing he did was provide a link to the ROM he had installed, nothing more, not even the tutorial related to it, I found that on my own (wait, he's made it more than clear how incompetent/ignorant I am as a person).
I've been searching and reading for 3 days straight now. Getting to the point again where I accept defeat, assume the money lost.
Moving on... I've rooted other phones before without issues.
I follow a tutorial on how to downgrade to a stock ROM.
http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
Odin stops with various errors.
I could still boot device into TWRP-3.1.0
Reflashed LineageOS 14.1 ROM from SD to get it working again.
LineageOS 14.1 ROM would boot up, run for almost a minute and a half and shut down.
Pull battery, reboot into LineageOS 14.1 ROM, same thing.
Run Odin, connect device to computer, try to flash stock ROM, error again (different one). Somehow, it says "There is no PIT partition"
I followed this tutorial: https://forum.xda-developers.com/no...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641
Odin says FAIL.
Now, it does NOTHING.
I follow this tutorial: Debrick here: https://forum.xda-developers.com/not...k-img-t3488114
Yes, the whole freezer thing overnight.
I have the latest USB drivers installed.
When I connected to the PC, an error popped up saying "...drivers not installed properly..." so I let Windows Update install the correct drivers.
I can connect to the PC now, press the power button for more than 10 seconds, eventually a popup message says "USB Device Not Recognized by Windows"
I've tried the following stock ROMs, 4.4.4, 5.1.1. I finally managed to download 6.0.1, but haven't been able to try it.
All I can say is that if you can boot into TWRP(I assumed you install the N910T version), then your phone is not bricked. All these "debricking" you're doing is potentially harming than fixing.
You assume the risk, when you buy 2nd hand. But based on what you're saying, it sounds like it may also have hardware issues(I don't think software will fix). Was it working when you got it? If you can return it, I suggest you do.
Another pc or windows version may work
A more trustworthy guide on using ODIN:
http://forums.androidcentral.com/am...w-flash-stock-rom-via-odin-new-interface.html
mnopy said:
Another pc or windows version may work
Click to expand...
Click to collapse
I will try with another PC, two batteries, different USB cables, different versions of the USB drivers, and so on.
Anything I missed?
ziggy1971 said:
I will try with another PC, two batteries, different USB cables, different versions of the USB drivers, and so on.
Anything I missed?
Click to expand...
Click to collapse
QualcommDrv
this is the Qualcomm Drivers(x86 and x64, choose your system's version and install) .
Without that your pc will not recognize your phone.
Uninstall everything related to samsung from your pc.
Kies, smart link, usb drivers. Use revo-unistaller for this to be sure nothing have left behind.
Go to control panel>system>device manager and remove anything that is related to your phone . If prompt delete drivers associated with that, say yes. Reboot your pc
Have saved QualcommDrv, samsung usb drivers and Odin. These are the tools you are going to need and must have.
after uninstall everything, unzip and install QualcommDrv.
Take off your battery, press power buton for 10 sec . Connect the phone to pc (without battery)
QualcommDrv will install the correct drivers for your phone. After that If in devices and printers it is recognized as Qualcomm 8084 .... its ok to proceed . if not , check again drivers and their installation
If windows says device drivers are not correctly installed and prompt to download and install, stop and cancel it.
IT will replace the QualcommDrv and you will not be able to see your phone correctly.
You need to keep QualcommDrv installed. When this is done and you are sure its correct and working, unplug your phone and install Samsung usb drivers. Reboot pc
unzip odin in desktop (or where ever its easy to access).
with your phone freezed and battery charged try to go to download mode. If succeed, connect to pc and with odin try to flash stock rom. If not ......
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
That what you need to have correct and working in order to START. THIS IS ONLY THE FIRST STEP
YOU HAVE TO UNDERSTAND
this is a hardware failure of the motherboard and will never will be completely fixed. These steps will only help you resurrect your phone and maybe give you the chance to be able to use it again.
It has nothing to do with software that failed to install. It was just the result and not the real problem, which is a diffect motherboard like thousand others. Sadly this is a common problem with Note 4 that happened to many users.
I have the same problem and I also bought it second hand knowing its problematic but not how much.
After that I realized the problem and the solutions to it. Every one of us is having a slightly different behavior of the phone.
I, for example cannt use the phone without the ext sdcard with unbrick image in it. When I take it out phone, will not start, reboot , do nothing.With the card in it its working almost perfect.
So have patience and read and search to know what you are dealing with.
Good luck
I managed to revive the Note 4 using a stock ROM.
Now, I have more questions like;
- Is this a problem on ALL models of the Note 4 or is it limited to a certain model?
ziggy1971 said:
I managed to revive the Note 4 using a stock ROM.
Now, I have more questions like;
- Is this a problem on ALL models of the Note 4 or is it limited to a certain model?
Click to expand...
Click to collapse
I don't believe you truly downgraded. I'm assuming you were on a 6.0.1 bootloader running a compiled 7.1.1 ROM. It probably hosed some partitions, and other things. Flashing the Stock ROM normalized it.
Most of time flashing a stock touchwiz rom will fix the "damage" that results in flashing a CM ROM.
dicksteele said:
I don't believe you truly downgraded. I'm assuming you were on a 6.0.1 bootloader running a compiled 7.1.1 ROM. It probably hosed some partitions, and other things. Flashing the Stock ROM normalized it.
Most of time flashing a stock touchwiz rom will fix the "damage" that results in flashing a CM ROM.
Click to expand...
Click to collapse
I have no idea what kernel, bootloader, etc. were/are used in the LineageOS ROM.
What I'd like to do is take a stock ROM and remove the unnecessary BLOATWARE and keep all the rest as it is.
Personal blurb: Why can't OS makers simply do that, make an OS!!! Windows, Android, it really doesn't matter, they're all the same.
ziggy1971 said:
I have no idea what kernel, bootloader, etc. were/are used in the LineageOS ROM.
What I'd like to do is take a stock ROM and remove the unnecessary BLOATWARE and keep all the rest as it is.
Personal blurb: Why can't OS makers simply do that, make an OS!!! Windows, Android, it really doesn't matter, they're all the same.
Click to expand...
Click to collapse
There is nothing stopping you from doing that but you.
Don't waste your breath saying I don't know how. There are TONS of guides on XDA.
That's exactly how I started learning. With that desire.
And here's what was most likely on it
https://forum.xda-developers.com/note-4/orig-development/rom-cyanogenmod-14-1-t3506613
dicksteele said:
There is nothing stopping you from doing that but you.
Don't waste your breath saying I don't know how. There are TONS of guides on XDA.
That's exactly how I started learning. With that desire.
And here's what was most likely on it
https://forum.xda-developers.com/note-4/orig-development/rom-cyanogenmod-14-1-t3506613
Click to expand...
Click to collapse
"I don't know how" generally isn't in my vocabulary. It's more like, where do I start, what do I need, where's a good tutorial explaining the what, how, and why of doing things.
Do I need to go all the way into the Java source code or are there other ways of removing some of the built-in apps?
Any tutorial/info suggestions are more than welcome. I'm not that familiar with the lingo of ROM customizing, so my searches are pretty much limited to that; "Android ROM customizing" is about the jist of it right now.
ziggy1971 said:
"I don't know how" generally isn't in my vocabulary. It's more like, where do I start, what do I need, where's a good tutorial explaining the what, how, and why of doing things.
Do I need to go all the way into the Java source code or are there other ways of removing some of the built-in apps?
Any tutorial/info suggestions are more than welcome. I'm not that familiar with the lingo of ROM customizing, so my searches are pretty much limited to that; "Android ROM customizing" is about the jist of it right now.
Click to expand...
Click to collapse
take a look here,
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
here:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and here:
https://forum.xda-developers.com/showthread.php?t=2467004
and maybe here:
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I cannt built but I can test, so go for it and tell us if we can help in the next step
logosA said:
take a look here,
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
here:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and here:
https://forum.xda-developers.com/showthread.php?t=2467004
and maybe here:
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I cannt built but I can test, so go for it and tell us if we can help in the next step
Click to expand...
Click to collapse
Those are good.
Some more are here
https://forum.xda-developers.com/general/xda-university
https://forum.xda-developers.com/chef-central/android
https://forum.xda-developers.com/showthread.php?t=1272270
https://forum.xda-developers.com/showthread.php?t=2069130
https://forum.xda-developers.com/showpost.php?p=5626301&postcount=4
https://forum.xda-developers.com/showthread.php?t=1590192
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
There are essentially two ways to do what you want.
Use the unpack tool above, extract the system.img from a Stock ROM
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
I get my stock ROMs from here
http://updato.com/firmware-archive-select-model?q=n910c&rpp=15&order=date&dir=desc
Remove the bloatware or apps you don't want.
Use the app same app that you used to extract the system.img to repack it.
Use the https://forum.xda-developers.com/chef-central/android/tool-afaneh-tar-kitchen-t3603649
to build a tar and flash with ODIN.
Second option use a kitchen. I'm testing the one below today to see if it works.
https://forum.xda-developers.com/ch...0-0-deluxe-kitchen-graphic-interface-t3579100
SuperR works great. But you need a Linux environment to run it.
I use virtualbox on my Win10 machine. I use premade images from here
http://www.osboxes.org/virtualbox-images/
Personally I use the Ultimate Edition.
Or use cygwin. I gave you plenty of links to learn how that works. It's a pain that's why I use virtualbox.
Hi All
Looking for a best tutorial to follow and the right one for my phone really don't want to brick it, obviously :/. as there seems to be a few versions for the S7
I have the following: S7 android 8.0.0 SM-G930F not sure what else I need to know! I'm in the UK so I assume UK phones come with Exynos cpu's
and as far as I am aware android 8 is Oreo! but when they say Stock Rom I assume they mean the same as what came with the phone the original rom?
if so is there an alternative stable rom without the crap included or is it just as simple to delete every thing you don't want now it's rooted! and does that mean if I reset the phone its back to normal with all the crap included! or is there a way to keep it rooted even after reset! and should anything be disabled I.e prepare the phone before attempting to root like any kind of auto encryption that needs disabling and just one more question
if at anytime the rooting process hangs for a ridiculous amount of time when should I throw in the towel! and what are the chances of retrieving the phone back to original state! or does a dirty shutdown brick it?.
I started the root process but failed at first hurdle!, followed instructions install Odin3_v3.13.1 but when I connected the phone nothing showed up in Odin? though I will have another go just to confirm I followed it correctly, I'll update this when it's done.
this was the tutorial I followed:
Easy 4 Newbie [Root Guide]SM-G930F, G935F, G930FD, G935FD (Samsung Galaxy S7 Edge)
Warning ! Please note that the official TWRP for Nougat on Galaxy S7/ S7 Edge is not available yet but based on my experience the Marshmallow version is working on Nougat. By installing a custom recovery on your S7 and S7 Edge and rooting it...
forum.xda-developers.com
I know alot of questions I would really appreciate any help and clarification on the above.
many thanks
Regards
Daz
Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.
Mohamedkam000 said:
Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.
Click to expand...
Click to collapse
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz
CitizenSmith said:
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz
Click to expand...
Click to collapse
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.
Mohamedkam000 said:
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.
Click to expand...
Click to collapse
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.
The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).
mooms said:
The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).
Click to expand...
Click to collapse
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.
CitizenSmith said:
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.
Click to expand...
Click to collapse
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.
Mohamedkam000 said:
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.
Click to expand...
Click to collapse
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.
CitizenSmith said:
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.
Click to expand...
Click to collapse
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.
CitizenSmith said:
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.
Click to expand...
Click to collapse
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html
Mohamedkam000 said:
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.
Click to expand...
Click to collapse
Hi
Yes I can transfer files.
Yes phone asks to allow or block file transfer and it ohone shows up in Devices and Drives list and I can access the phone directory and shows up as Samsung s7 icon.
I will try another USB lead but the one I'm using is new and wasn't cheap but still a possibility I have had leads that weren't suitable for other things I was trying so it is worth a try.
Thanks
mooms said:
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html
Click to expand...
Click to collapse
When I downloaded Odin this was latest one Odin3_v3.13.1 though I have doubts that one version update will fix this issue as I did not see many if any people having my issue so they all used Odin and I believe theirs are fine even with older versions! but as I said Mohamedkam it's worth a try I will down load that version and give it a try.
As for the Samsung usb driver I believe that is where I got mine
SAMSUNG_USB_Driver_for_Mobile_Phones no version visible under properties on file version 1.7.23.0.
The USB connection seems to be fine I have uninstalled then re-download and reinstalled a couple of times.
I can transfer files no problem it shows up as Galaxy S7 Icon with card and phone drive inside.
I'll update shortly thank you.
Update:
I just went to try new Odin and whilst checking my phone have seen I have Offical TWRP app installed? I have no clue as to how that's got in there! as Odin did not show phone so I could select nothing!.
In the phone I open app and if i select backup existing recovery it opens and Select Folder tab and under that Selected Folder: /sdcard Filename: Recovery .img and at the bottom of screen Root access required.
I just hope it's installed correctly!. it is showing in playstore my apps as well just to confirm. if this is now installed what should I do next Now not sure what tutorial to start following.
I am just going to try the new odin and see if it picks up the phone back soon.
OK Seem that it now shows up in the new Odin. at least I think it has! in the log window I see this: <ID:0/004> Added!!
I didn't see that before.
Would be grateful if you could tell me how to proceed from here!
Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr
mooms said:
Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr
Click to expand...
Click to collapse
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
CitizenSmith said:
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.
CitizenSmith said:
still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com
Mohamedkam000 said:
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.
Click to expand...
Click to collapse
Yer I read that but I've ended up with TWRP installed and did not do that process because I was unaware it installed until it showed up.
As I said I'll just keep looking for now I know I'll find one that works for me from start to finish.
and I've been checking youtube but wouldn't want to use any links their providing but it may help familurise myself with the whole process if i watch enough of them.
Thanks again for your help.
mooms said:
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi Mooms
I will check that out many thanks. I wonder if you could help me here. I am in the middle of the rooting process but have hit a snag. again!
I have now installed TWRP successfully then no-verity-opt-encrypt-3.1 all went fine and I'm at point of flashing Magisk but have an issue when I swipe to flash is gives me a error in red saying "invalid zip file format !"
I downloaded it from github here.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I click on "code" tab and then "download zip" and I placed that in a download folder on my sd card when I select it I get the above error any ideas as to why I am getting this am I downloaded the correct file?
thanks for any assistance you could give.
Anyone have the Android 12 firmware that Cricket released from this Reddit thread? There is one custom rom developed in this XDA thread but not sure how stable it is.
Hey dude, I'm currently using the a teams custom ROM From here.
I've used all three attached, only issues I found in them are as followed
Android 12 rom's Bluetooth will connect but won't send audio, to fix this go to settings/phh settings/misc/ there you'll find a bunch of options, Im using Android 11 rn so I can't tell u which one needs to be enabled ATM
Android 11 one doesn't have this issue, and all three won't allow lock screen or fingerprint, I couldn't find a fix for this)
Riotruth said:
Hey dude, I'm currently using the a teams custom ROM From here.
I've used all three attached, only issues I found in them are as followed
Android 12 rom's Bluetooth will connect but won't send audio, to fix this go to settings/phh settings/misc/ there you'll find a bunch of options, Im using Android 11 rn so I can't tell u which one needs to be enabled ATM
Android 11 one doesn't have this issue, and all three won't allow lock screen or fingerprint, I couldn't find a fix for this)
Click to expand...
Click to collapse
Thanks for the reply.
I'm a little confused with the aio toolkit requirement.
1. Is the aio toolkit is to help install TWRP and Magisk?
2. Where is the download link to aio toolkit?
3. How do you install the aio toolkit?
I couldn’t tell you on that, I never played around with it. Over on that thread you get 3 downloads, 2 android 12 gsm, and 1 android 11 gsm.
I
They all come with magisk pre installed, all you need is TWRP.
Riotruth said:
I couldn’t tell you on that, I never played around with it. Over on that thread you get 3 downloads, 2 android 12 gsm, and 1 android 11 gsm.
I
They all come with magisk pre installed, all you need is TWRP.
Click to expand...
Click to collapse
Ok. That's what I have in mind too. Normally you need to unlock bootloader and then install TWRP before you can flash the custom rom.
I thought the aio toolkit include the TWRP and Magisk. So you install it then boot to the stock recovery to flash the rom.
Yeah. Theres another post here for getting just twrp and magisk. I'm to lazy to quote it lol, but that's how I got it originally, I then flashed these ROM's without a issue.
Riotruth said:
Yeah. Theres another post here for getting just twrp and magisk. I'm to lazy to quote it lol, but that's how I got it originally, I then flashed these ROM's without a issue.
Click to expand...
Click to collapse
I finally installed the custom GSI roms. There is one major issue is that the phone don't ring for incoming calls. After 5 rings, it goes to the voicemail. I can make calls.
Did you have this problem? Which rom are you using?
I installed TWRP using AIO Toolkit. Not sure how you install your TWRP.
I wonder if the modified boot.img from Magisk might be the cause to the phone ring issue since my stock ROM is updated to Android 11 2023 February. The developer created the custom GSI roms and TWRP and Pre-patched using an older Android 11 in May 2022.
magi44ken said:
I finally installed the custom GSI roms. There is one major issue is that the phone don't ring for incoming calls. After 5 rings, it goes to the voicemail. I can make calls.
Did you have this problem? Which rom are you using?
I installed TWRP using AIO Toolkit. Not sure how you install your TWRP.
I wonder if the modified boot.img from Magisk might be the cause to the phone ring issue since my stock ROM is updated to Android 11 2023 February. The developer created the custom GSI roms and TWRP and Pre-patched using an older Android 11 in May 2022.
Click to expand...
Click to collapse
hi.
i have not noticed that at all. but i dont do calls lol.
i installed twrp myself, and am using the roms. would you mind explaining how you used AIOToolkit?
Riotruth said:
hi.
i have not noticed that at all. but i dont do calls lol.
i installed twrp myself, and am using the roms. would you mind explaining how you used AIOToolkit?
Click to expand...
Click to collapse
1. AiO Toolkit
Sure. In case you don't have a copy of the full AIO Toolkit that includes unbrick roms and rooted stuff. I upload a lite of the AIO Toolkit that includes only the rooted stuff, not full rom. It's only 360MB.
Public - Google Drive
drive.google.com
You will have to use Linux in order. I recommend Ubabutu v22 instead v23. I couldn't get it work in Windows.
Follow the direction in the readdme.md to install MTKClient and requirements: https://github.com/bkerler/mtkclient
After completing the installation, make sure you enable USB debugging and run `adb devices` and confirm to enable "Allow to use usb debugging" in the phone.
Run the AIO Toolkit CLI script: Main_Menu.sh. The simplest way to run this Main_Menu.sh is open the File Manager and right click on it and select Run. It will give you instruction what to do after you select the menu choice.
In the main meanu, select the bootloader menu item for unlocking the bootloader and select recovery menu item installing TWRP and Magisk.
If it ask to enter brom mode, just power off the phone, hold the volume up and down buttons for 2 seconds and connect the USB cable to PC. It should automatically recognize and do it stuff.
2. Bluetooth Fix
Also there is a fix for bluetooth by enabling this settings in any of the custom rom you use.
Go Settings > Phh Settings > Misc Features. Under Other section, check "Force disable A2DP Offline"
3. Phone call ring
Can you do a quick call test for me if you don't mind? Just have someone call your Dream 5G phone. If it rings, it means it works. If it works, can you list baseband version and custom rom you are using?
I really wanted to use Android 12 if I can fix the phone call ringg issue.
4. TWRP v3.7 update?
What version of TWRP are you using? is 3.6.x? Have you upgrade to v3.7x that is fully Android 12 compatiable?
I was going to do the manual process but there was only threads about it and not sure how relaible. So I use the AIO Toolkit.
However if you able to upgrade to v3.7, please share the steps.
Let me know if you need to help.