[TWRP][v3.1.1][xt907][KKBL][EXPERIMENTAL]TWRP for xt907 KKBL EXPERIMENTAL build - Droid RAZR M General

TEAMWIN TWRP v3.1.1 for the RAZR M KKBL (xt907 KKBL)
Built from source: http://github.com/minimal-manifest-twrp/platform_manifest_twrp_lineageos.git
All the usual prefaces to using this project. ie/eg I am not responsible for anything if you flash this zip in regards to your device or data etc etc etc
I have built this blindly (ie NO testing whatsoever) as I only have a JBBL device. It was easy for me to build since I have built a JBBL version, and I thought someone may find it useful IF it worked.
Please let me know if it works for you?

DiamondJohn said:
Please let me know if it works for you?
Click to expand...
Click to collapse
No-one has tried it?

Works like a charm for me

Worked like a charm here.

Shmaks said:
Works like a charm for me
Click to expand...
Click to collapse
trivialPotato said:
Worked like a charm here.
Click to expand...
Click to collapse
Now you just have to find a KKBL ROM to use it against :fingers-crossed: but maybe this will be a case of now that a way to flash it has been made, "build it and they will come"

Works great so far, just about to try a lineage rom.
DiamondJohn said:
TEAMWIN TWRP v3.1.1 for the RAZR M KKBL (xt907 KKBL)
Built from source: http://github.com/minimal-manifest-twrp/platform_manifest_twrp_lineageos.git
All the usual prefaces to using this project. ie/eg I am not responsible for anything if you flash this zip in regards to your device or data etc etc etc
I have built this blindly (ie NO testing whatsoever) as I only have a JBBL device. It was easy for me to build since I have built a JBBL version, and I thought someone may find it useful IF it worked.
Please let me know if it works for you?
Click to expand...
Click to collapse
Will keep you posted.

For anyone wanting to try this just a pointer. This isn't a TWRP flashable zip so you will need to use your computer to extract the IMG file and sideload using fastboot. Working great so far.

Does this require an unlocked bootloader? I am rooted.
---------- Post added at 01:36 AM ---------- Previous post was at 01:35 AM ----------
DiamondJohn said:
Now you just have to find a KKBL ROM to use it against :fingers-crossed: but maybe this will be a case of now that a way to flash it has been made, "build it and they will come"
Click to expand...
Click to collapse
I have XT907 KitKat 4.4. ready to try. Just need to know if I need an unlocked bootloader. That said, I am rooted.

DragonFire1024 said:
Does this require an unlocked bootloader? I am rooted.
I have XT907 KitKat 4.4. ready to try. Just need to know if I need an unlocked bootloader. That said, I am rooted.
Click to expand...
Click to collapse
you MUST have an unblocked bootloader to flash a custom recovery. ie this.

DiamondJohn said:
you MUST have an unblocked bootloader to flash a custom recovery. ie this.
Click to expand...
Click to collapse
I only asked because 1) wasn't mentioned in this thread specifically. 2) Not all devices require the bootloader be unlocked. 3) Why does it need to be a custom recovery? I still get confused about that from time to time because it just amazes me that it seems that's where things seem to always end up and sometimes seems to be a bit too convenient. I'm not vastly familiar with bootloader technology so that's where I scratch my head. I can install TWRP, get to all the settings and options, so why can't I just back up the proper files/imgs and flash the zip?
Looks like I'm going to have to rely on Sunshine then. I wish they accepted Bitcoin. It's that, or lose the phone to old age as it's components and functions fail slowly, one by one. I know I can reflash the stock firmware, it's been done a...few...times.
EDIT: Well s**t. Sunshine DOES accept Bitcoin. If I had known that ages ago...ugh

Just wanted to pass on this TWRP build for KKBL worked great. I ended up "downgrading" to JBBL in order to load a current LineageOS build.

It appears it was just me
I re-flashed my bootloader upgrade CAREFULLY via fastboot, and the error on wiping cache disappeared. however, I still haven't been able to flash a bootable KKBL ROM. It was suggest via PM that I also wipe my internal SDCard, which I have yet to try.
Shmaks said:
Works like a charm for me
Click to expand...
Click to collapse
trivialPotato said:
Worked like a charm here.
Click to expand...
Click to collapse
mr3p said:
Just wanted to pass on this TWRP build for KKBL worked great. I ended up "downgrading" to JBBL in order to load a current LineageOS build.
Click to expand...
Click to collapse
I see the posts saying it works, but has anyone actually successfully flashed and booted (ie past the bootanimation ) any ROM Zip file using this recovery?
Or performed a backup and restore?
I ask this as I finally got around to creating an upgrade (from JBBL to KKBL) for my phone (an xt905 not an xt907) and the two ROMs I tried both boot looped on the bootanimation. Also, I get errors when i try to wipe my cache.
Is it just me?
-----edit-----
I got a PM saying that someone has managed to flash an LP ROM for KKBL using this recovery. So obviously I need to go back to the drawing board on my upgrade to KKBL...

I am considering adding PDS (ie FSD) backup to my TWRP builds see https://forum.xda-developers.com/showpost.php?p=74136332&postcount=9 it also applies to KKBL.

DragonFire1024 said:
I only asked because 1) wasn't mentioned in this thread specifically. 2) Not all devices require the bootloader be unlocked. 3) Why does it need to be a custom recovery? I still get confused about that from time to time because it just amazes me that it seems that's where things seem to always end up and sometimes seems to be a bit too convenient. I'm not vastly familiar with bootloader technology so that's where I scratch my head. I can install TWRP, get to all the settings and options, so why can't I just back up the proper files/imgs and flash the zip?
Looks like I'm going to have to rely on Sunshine then. I wish they accepted Bitcoin. It's that, or lose the phone to old age as it's components and functions fail slowly, one by one. I know I can reflash the stock firmware, it's been done a...few...times.
EDIT: Well s**t. Sunshine DOES accept Bitcoin. If I had known that ages ago...ugh
Click to expand...
Click to collapse
The boot loader has to be unlocked because of the nature of the boot loader itself. I ain't no expert, but based on my understanding and what I personally know, here is what a boot loader does:
A boot loader checks the various images (recovery, boot, radio, etc.) and if any of these are incorrect/unsigned (like a custom recovery), your device won't boot. This makes sense, because most users aren't flashing their devices, so when an image is unsigned something is VERY WRONG. Unlocking a boot loader basically turns off the signature check that the boot loader does. If the boot loader isn't checking each image than it will boot up fine whether you have a custom recovery or not.

Recently reacquired an xt907 after "losing" mine. Anyways I rooted with Kingroot and used the mrw root.sh script to switch to supersu. I had to use an older version if kingroot, 4.9.6 for it to work. I then used the Sunshine app to unlock bootloader for $25 and used terminal emulator to 'dd' TWRP to recovery. Everything is perfect and am glad all still works as such.
Now my point: is there an easy guide or something that I can use to port an updated TWRP image? May thanks to everything.

DragonFire1024 said:
Recently reacquired an xt907 after "losing" mine. Anyways I rooted with Kingroot and used the mrw root.sh script to switch to supersu. I had to use an older version if kingroot, 4.9.6 for it to work. I then used the Sunshine app to unlock bootloader for $25 and used terminal emulator to 'dd' TWRP to recovery. Everything is perfect and am glad all still works as such.
Now my point: is there an easy guide or something that I can use to port an updated TWRP image? May thanks to everything.
Click to expand...
Click to collapse
Easy is a relative scale to the person asking the question. Read and answer it for yourself. TWRP builds are muuuuuch simpler than ROM builds.
The following two may mean you do not have to build. I have never used them, as I built mine from source.
https://forum.xda-developers.com/android/general/unofficial-twrps-devices-source-code-t3833338
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
https://forum.xda-developers.com/showthread.php?t=1943625
The question may also be better asked, after reading, in the thread above

Related

Successfuly used FIREWATER & now need correction on next steps

Last time I rooted a phone was the original DROID (great phone).
Now, I'm back on the scene after not fond of the OTA 4.4 so I consider myself a "newbie" since things have changed a lot.
Took some time but managed to successfully use FIREWATER.
Just wondering if I have the correct order of the next steps:
(*Verizon One w/ Mac machine only)
1. FIREWATER
2. Find Recovery to flash
3. Make back-up
4. Root
5. Find desired ROM
So looks like RECOVERY is next but there are MANY links with "recovery" in search results it's a bit overwhelming.
Obviously I need one specifically for Verizon, right?
Thanks in advance
Your phone was android 4.4.2 and you were able to use firewater to unlock? Or are you asking if you can use it to root 4.4.2? Firewater doesn't work the ota we just got.
Sent from my HTC6500LVW using Tapatalk
Everything you need can be found HERE everything is pretty much up to date recovery wise
Everyone has their preferences as what recovery to use but I just went through this about 4 days ago.
A recovery option that will work: http://forum.xda-developers.com/showthread.php?t=2416273
See downloads where it says classic, and touch -- it's your choice which to get.
I will however note that I had an issue wiping cache/data on the 6.0.4.7 update. It might of just been a bad flash but I ended up going to version 6.0.4.4 and I was able to do everything just fine. Mounts/unmounts, backups/restores, wipes and flashes.
Link to the version I used (CWM Classic 6.0.4.4): http://www.radracer.us/otp/droid/recovery-clockwork-6.0.4.4-m7vzw.zip
To get into your recovery you go to your bootloader (or whatever HTC calls it, where you see Fastboot, HBoot version and what not), and you will see Recovery as an option. Once selected you will boot into CWM.
Do you lose data if you use firewater? From what I am reading I dont believe data is lost but haven't seen a clear answer.
disconnecktie said:
Your phone was android 4.4.2 and you were able to use firewater to unlock? Or are you asking if you can use it to root 4.4.2? Firewater doesn't work the ota we just got.
Click to expand...
Click to collapse
No no, sorry should've clarified that: I was on 4.3 and saw the unnecessary changes 4.4.2 brought so I withheld from updating.
onthehole said:
Do you lose data if you use firewater? From what I am reading I dont believe data is lost but haven't seen a clear answer.
Click to expand...
Click to collapse
No, not at all. I think I will lose data when I flash recovery or install a ROM though
vpxf said:
Everyone has their preferences as what recovery to use but I just went through this about 4 days ago.
A recovery option that will work: http://forum.xda-developers.com/showthread.php?t=2416273
See downloads where it says classic, and touch -- it's your choice which to get.
I will however note that I had an issue wiping cache/data on the 6.0.4.7 update. It might of just been a bad flash but I ended up going to version 6.0.4.4 and I was able to do everything just fine. Mounts/unmounts, backups/restores, wipes and flashes.
Link to the version I used (CWM Classic 6.0.4.4): http://www.radracer.us/otp/droid/recovery-clockwork-6.0.4.4-m7vzw.zip
To get into your recovery you go to your bootloader (or whatever HTC calls it, where you see Fastboot, HBoot version and what not), and you will see Recovery as an option. Once selected you will boot into CWM.
Click to expand...
Click to collapse
That's a lot and after this busy weekend, I'll have to sit down and go through everything you just posted. Thanks!
BTW I'm seeing that there are some issues with TWRP not allowing you to BOOT back up if your phone dies?
Any reason why TWRP should be the one or do another RECOVERY?
-XIV- said:
No no, sorry should've clarified that: I was on 4.3 and saw the unnecessary changes 4.4.2 brought so I withheld from updating.
Click to expand...
Click to collapse
Im in the same boat as you. Waiting to see how everything works out. I have heard clockwork is working pretty well for this phone. ALmost ready to S-OFF now.
So, if I S-Off on 4.3, can I then let the ota come over and not lose the abililty to flash SU, or a rom with SU/Root? I should still be able to flash anything I want in recovery with S-OFF no?

[Q] TWRP replaced with stock recovery[t805]

I have flashed twrp recovery over odin. I can only get into stock recovery though. Usual fix would be to remove battery b4 rebooting, but I can not make out the battery on this device - seems integrated / hidden.
I am running 4.4.2 KitKat. Trying to root it to debloat.
Any ideas? Maybe remove some startup scripts or Idk...
EDIT: I got word that it seems to be either some hash verification in the new android 4.4.x kernel or even a locked bootloader on top. Is that correct? And, if so, what would be a good course of action now?
More info can be found imo when googling for
Android 4.4 KitKat: Google Making Root Without Unlocked Bootloader Difficult?
Click to expand...
Click to collapse
(sry can't link)
JoeRifle said:
I have flashed twrp recovery over odin. I can only get into stock recovery though. Usual fix would be to remove battery b4 rebooting, but I can not make out the battery on this device - seems integrated / hidden.
I am running 4.4.2 KitKat. Trying to root it to debloat.
Any ideas? Maybe remove some startup scripts or Idk...
EDIT: I got word that it seems to be either some hash verification in the new android 4.4.x kernel or even a locked bootloader on top. Is that correct? And, if so, what would be a good course of action now?
More info can be found imo when googling for (sry can't link)
Click to expand...
Click to collapse
I don't know of any tablet that has user removable battery. I'm sure you have to be rooted before you can install a custom recovery. Are you using the rooting method in the development topic?
The question would be why you didn't use the recommended way of using Flashify to flash twrp?
Eddie Hicks said:
I don't know of any tablet that has user removable battery. I'm sure you have to be rooted before you can install a custom recovery. Are you using the rooting method in the development topic?
Click to expand...
Click to collapse
Yes. Would have posted there too had it been allowed. It is the method described in the t800 thread, where it says you should flash twrp via odin and then install SuperUser zip in TWRP.
kenkiller said:
The question would be why you didn't use the recommended way of using Flashify to flash twrp?
Click to expand...
Click to collapse
I thought that this was the way to do it. I have not read anything in that thread about flashify.
If flashify works with Android 4.4.2 I will dig into that. Does it?
JoeRifle said:
Yes. Would have posted there too had it been allowed. It is the method described in the t800 thread, where it says you should flash twrp via odin and then install SuperUser zip in TWRP.
I thought that this was the way to do it. I have not read anything in that thread about flashify.
If flashify works with Android 4.4.2 I will dig into that. Does it?
Click to expand...
Click to collapse
You did not follow the instructions in the first post, but the latter ones posted by bodivas? Then you should consider trying those in the first post - they work for T805 as well.
The ones in the first post work. Flashify I found it in the CF-Root for T700 thread, it works fine on T805 as well, as long as you get the correct img file from the TWRP site.
kenkiller said:
You did not follow the instructions in the first post, but the latter ones posted by bodivas? Then you should consider trying those in the first post - they work for T805 as well.
The ones in the first post work. Flashify I found it in the CF-Root for T700 thread, it works fine on T805 as well, as long as you get the correct img file from the TWRP site.
Click to expand...
Click to collapse
yes bodivas is his name. it seemed to be the better method. but since it did not "accept" the image, although odin said success, I dug deeper and found out that there is supposed to be a hash check in 4.4.2 which keeps me from keeping the flashed image
Will flashify solve that problem and make TWRP "resident"? I would rather not flash the CF Auto since it is for a t800 not t805, but maybe i am overcautious:angel:
JoeRifle said:
yes bodivas is his name. it seemed to be the better method. but since it did not "accept" the image, although odin said success, I dug deeper and found out that there is supposed to be a hash check in 4.4.2 which keeps me from keeping the flashed image
Will flashify solve that problem and make TWRP "resident"? I would rather not flash the CF Auto since it is for a t800 not t805, but maybe i am overcautious:angel:
Click to expand...
Click to collapse
You don't get by in XDA by being cautious in everything. There's enough reports to tell otherwise.
Yes, using Flashify to flash TWRP replaces stock recovery. TOTALLY.
Requires root though right? So is not possible for me I fear Only way would then be CF Auto for t800...as we found out. TU anyhow.
JoeRifle said:
Requires root though right? So is not possible for me I fear Only way would then be CF Auto for t800...as we found out. TU anyhow.
Click to expand...
Click to collapse
Of course it requires root. Not possible because you don't dare to flash the T800 files? Hehe.....you're gonna have a hard time here.
kenkiller said:
Of course it requires root. Not possible because you don't dare to flash the T800 files? Hehe.....you're gonna have a hard time here.
Click to expand...
Click to collapse
I just need to get the hang of these appy lil spy thingy thing things...god knows what g**gle has in store for you. out of curiosity, so you are saying there is no hash check in the bootloader keeping me/us from doing our evil deeds? how about the article up there I quoted, and what the heck happened when i odined TWRP?
just asking...will flash the CF. so lets cross thumbs and make tha knox trip count
Hi Guys. As following the instructions to flash openrecovery-twrp-2.8.0.1-chagallwifi.tar using Odin3 v3.09, my T805 reboots into recovery, the TWRP boot screen is blurred, and after the Menu appears, my device locks up and there is no way to reboot it. Force reboot by holding down the Power button doesn't work. I've been trying for nearly an hour and nothing works. The Task Menu and Return buttons are lit, but the screen is blank. Any suggestions on how to get my T805 to reboot normally?
Thanks.
UPDATE:
I found that 2.8.0.1 appears out of alignment on the screen, and I had to poke around until I found where the Reboot button was located. By chance I got it to go into Bootloader and the system rebooted. Once online I installed Flashify and installed TWRP 2.7.1.1 and SUCCESS!! Now my T805 is working normally. WHEW!!

advice please

was wondering can i just root my m8 without flashing recovery all i want is to install adaway to block ads thats if someone could please advise
Depending on what build you are on (newer ones can't go it), you may be able to fastboot boot recovery instead of flashing recovery. Once booted into recovery, you can flash SU or SuperSU.
You need to be bootloader unlocked either way. So I actually don't see a point in doing what you ask. Once you root, you can always install stock recovery again.
redpoint73 said:
Depending on what build you are on (newer ones can't go it), you may be able to fastboot boot recovery instead of flashing recovery. Once booted into recovery, you can flash SU or SuperSU.
You need to be bootloader unlocked either way. So I actually don't see a point in doing what you ask. Once you root, you can always install stock recovery again.
Click to expand...
Click to collapse
ok thanks i get phone tomorrow so will give it a go i used to have s5 which was easy to root this sounds complicated
pnr2020 said:
ok thanks i get phone tomorrow so will give it a go i used to have s5 which was easy to root this sounds complicated
Click to expand...
Click to collapse
Every device and manufacturer has its own subtle differences and learning curve. Its really not what hard, just read up and make sure you understand before messing around with it.
pnr2020 said:
was wondering can i just root my m8 without flashing recovery all i want is to install adaway to block ads thats if someone could please advise
Click to expand...
Click to collapse
Follow this guide for rooting.
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
but as redpoint73 said you have to unlock bootloader and install custom recovery.
Rantrave07 said:
but as redpoint73 said you have to unlock bootloader and install custom recovery.
Click to expand...
Click to collapse
That is not exactly what I said. If the phone is 4.4.3 or 4.4.2, OP should be able to fastboot boot recovery without flashing it. Then flash SU/SuperSU. I've seen others do it this way, although I personally don't see much point to it.
But yes, bootloader still needs to be unlocked.
redpoint73 said:
That is not exactly what I said. If the phone is 4.4.3 or 4.4.2, OP should be able to fastboot boot recovery without flashing it. Then flash SU/SuperSU. I've seen others do it this way, although I personally don't see much point to it.
But yes, bootloader still needs to be unlocked.
Click to expand...
Click to collapse
yeah one can always flash the stock recovery after rooting.
redpoint73 said:
That is not exactly what I said. If the phone is 4.4.3 or 4.4.2, OP should be able to fastboot boot recovery without flashing it. Then flash SU/SuperSU. I've seen others do it this way, although I personally don't see much point to it.
But yes, bootloader still needs to be unlocked.
Click to expand...
Click to collapse
Booting it instead of flashing it is better if you want to make a backup of stock recovery. Especially if it's Philz that you're booting since TWRP doesn't seem to make backups of the stock recovery anyways.
Using the dd command to make a "copy" of the recovery works if you're rooted and to be rooted you have to have custom recovery which doesn't help much since you lose stock recovery the moment you flash the custom one, but if you boot it and root then at least you can use the dd command if that is the way you want to make a "backup" of your stock recovery. Silly little circle to run around in
BerndM14 said:
Booting it instead of flashing it is better if you want to make a backup of stock recovery. Especially if it's Philz that you're booting since TWRP doesn't seem to make backups of the stock recovery anyways.
Click to expand...
Click to collapse
Yes, I was aware of that; although it didn't seem to be the OP's goal. But thanks for pointing it out for their benefit.
thanks everyone for advice im sure i will get it right just one more quick question can you still upgrade with OTA when rooted or is it like other phones where you can not
Rantrave07 said:
Follow this guide for rooting.
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
but as redpoint73 said you have to unlock bootloader and install custom recovery.
Click to expand...
Click to collapse
thank you for the guide that makes it sound straight forward
pnr2020 said:
thank you for the guide that makes it sound straight forward
Click to expand...
Click to collapse
:good: glad it helped
The m8 was a little complicated at first than my previous phone the nexus 5 but I figured out the m8 and I love it a lot more than my n5
spinninbsod said:
The m8 was a little complicated at first than my previous phone the nexus 5 but I figured out the m8 and I love it a lot more than my n5[/QUOE
At first i wasn't sure i liked it but im getting used to it. When lollypop comes out do i need to restore to stock or can i just OTA and root again
Click to expand...
Click to collapse
pnr2020 said:
spinninbsod said:
The m8 was a little complicated at first than my previous phone the nexus 5 but I figured out the m8 and I love it a lot more than my n5[/QUOE
At first i wasn't sure i liked it but im getting used to it. When lollypop comes out do i need to restore to stock or can i just OTA and root again
Click to expand...
Click to collapse
To get updates you need a stock ROM unmodified, it can be rooted just do not mess with build.prop or platform.xml. However, to be able to install updates you need a stock recovery.
Click to expand...
Click to collapse
XSL-FO said:
pnr2020 said:
To get updates you need a stock ROM unmodified, it can be rooted just do not mess with build.prop or platform.xml. However, to be able to install updates you need a stock recovery.
Click to expand...
Click to collapse
thank you for info so if i stay on stock rom rooted i will have no trouble installing lollypop when released
Click to expand...
Click to collapse
pnr2020 said:
XSL-FO said:
thank you for info so if i stay on stock rom rooted i will have no trouble installing lollypop when released
Click to expand...
Click to collapse
As long as you have a stock recovery it's all good. But even if you have a custom one, before doing the update install a custom recovery. Make the update, and after that if you want flash again a custom recovery.
Click to expand...
Click to collapse

[Solved] Need help with installing Cyanogenmod (Without a PC if possible)

Hi all, new to all of this. Please keep this in mind as you read this thread.
Well first of all I have been reading about Cyanogenmod and how it helps saves battery. I also wanted to use cputuner to overclock my phone a little. I have in the past rooted this phone and installed cputuner not knowing that it could damage your phone if you didn't have a custom kernel that supported overclocking. After I found that out I uninstalled it and unrooted in fear of damage to my phone. Anyways I have a few questions and was looking knowledge, resources, and help about a few things.
Questions:
Is installing a custom rom and things needed to install a custom rom possible with a PC?
Can I safely reroot my device since I unrooted through #SU?
What do I need to do besides reroot my device in order to install a custom rom? (Cyanogenmod)
Thanks in advance!
Other INFO:
My device is a Samsung Galaxy S3 I-747
Firmware 4.4.2 KitKat
Device was rooted before using towelroot but I unrooted using #SU.
.
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
jason2678 said:
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
KentuckyGuy447 said:
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
Click to expand...
Click to collapse
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
dawgdoc said:
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
Click to expand...
Click to collapse
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
KentuckyGuy447 said:
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
Click to expand...
Click to collapse
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
dawgdoc said:
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
Click to expand...
Click to collapse
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
KentuckyGuy447 said:
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
Click to expand...
Click to collapse
I'm stuck.
You can install a custom recovery without having root, if you have a PC. You would use either Odin, Heimdall, or maybe adb.
You can install a custom recovery without a PC if you have root. You would use an app Like Flashify, Rom Manager, or Goo Manager (if it still exists).
You can flash a rom without a PC if you have a custom recovery, root is not needed.
Some roms, usually stock, can be flashed without a custom recovery if you have a PC.
I don't know the solution until you have access to a PC. I could see it being possible using a live USB with persistence of a Linux distribution, but you still have need for a PC. It's been a while since I created a live USB. The method I used required a small installation on the PC. so I don't see this as an immediate solution for you.
Oh sorry. I don't think towelroot works once you're on nj1, unless it has been updated.
If you get access to a PC, rooting is still fairly easy. You can use download mode and odin or heimdall to flash a custom recovery (be sure to uncheck reboot if using odin, or be really ready to pull battery). Don't let your phone reboot normally, you'll have to pull battery once odin is done.
Reboot to custom recovery, then flash supersu and you'll be rooted again, and set up to do whatever you want with your phone.
Sent from my LG-V410 using XDA Free mobile app
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
KentuckyGuy447 said:
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
Click to expand...
Click to collapse
excuse for butting in .... but if you dont know your bootloader/modem info. here is an app called 'samsung info' that should tell you.
your question "...... but theres no bootloader for my phone model right?" kinda worried me. its important to know because they should match AND trying to downgrade can brick your device. on the plus side ; i've never seen a custom ROM include bootloader/modem in it.
again , just a thought and not trying to butt in.:good:
https://www.dropbox.com/s/4ka74x02tg1rrn1/org.vndnguyen.phoneinfo-1.apk?dl=0
"all i can really do , is stay out of my own way and let the will of heaven be done"
As mrrocketdog stated, the Samsung Info app will tell you your bootloader and modem. If what you previously stated is correct, they should both be NJ1. You can get the same info by issuing these commands in a terminal emulator on the phone:
Code:
getprop ro.bootloader
and
Code:
getprop | grep version.baseband
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
KentuckyGuy447 said:
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
Click to expand...
Click to collapse
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
You have lifted a burden off my shoulders friend! Ever since I wanted to flash a custom Rom I've been worried if my phones bootloader was locked! I can now be at ease now that I know its unlocked. Will check upon that info about bootloader/modem.
Here is the info mrrocketdog
Is there a reason you can't use a PC to install a ROM?
I'm asking because I also do not know of a way to install a ROM without having root.
If you are able to root, you could try using the CM installer again.
audit13;5898140 said:
Thanks friend no worries, mrrocketdog helped me figure it out, than to all who helped!
Click to expand...
Click to collapse
KentuckyGuy447 said:
Here is the info mrrocketdog
Click to expand...
Click to collapse
Those are the latest versions of the bootloader and modem. You will be good for CM 12 or CM 11, and other custom ROMs based on CM. Older versions will work with them, but you probably need to edit the updater-script. (The older versions are not likely to include the NJ1 versions in the checks as they were not out when the ROMs were last updated.) NJ1 will also work with any of the ROMs based on the KitKat TouchWiz releases by Samsung.
As soon as you can find a PC to borrow you should be in business. Any chance of using one at a public library?
Appreciate all the help you gave me too friend, providing the links to cm and gapps, gonna borrow my friends laptop Sunday and try to root flash C-F Root through Odin. Thats the part that scares me but I should be good as people has confirmed it works for NJ1. Wish me luck friend. Would you recommend installing CM12? I personally like kit Kat and I know CM11 is based on that but is CM12 better? I guess its based on Lollipop

What happens if flash fails?

I'm somewhat certain I already know the answer to this but I just need confirmation.
With a locked bootloader, flashing anything other than stock will be unsuccessful, right? I've just rooted my t807a and am looking to get xposed running. I just don't want to brick this thing now that I've FINALLY got it rooted.
So what's the bad? What happens if I try to flash a custom recovery? Will it flash and then not work? Will it fail to flash? Will I be bricked/caught in a bootloop?
Right off the bat, let me make one thing abundantly clear: I do not care if I trip Knox. I assume the warranty is voided as soon as I take a new device out of the box so I really don't care if Samsung or AT&T finds out that I've been misbehaving.
In case it matters:
Model: SAMSUNG-SM-T807A
Android version: 5.0.2
Baseband version: T807AUCU1BOD4
Kernel version: 3.4.39-4727547
Build number: LRX22G.T807AUCU1BOD4
Device Status: Custom
Okay I'm no genius, but maybe do a search on using the app flashify to flash custom recovery (twrp) ......obviously the right file for your device.
I've used thus before on other devices and it work well but do your research . Flash at own risk.
Sent from my SM-T800 using Tapatalk
DO NOT flash a custom recovery or kernel on a bootloader locked device!
Unless you want a nice brick.
If you want xposed use Flashfire.
ashyx said:
DO NOT flash a custom recovery or kernel on a bootloader locked device!
Unless you want a nice brick.
If you want xposed use Flashfire.
Click to expand...
Click to collapse
Just to make sure I understand what you're telling me: even with a locked bootloader, it should be safe to use Flashfire to apply the xposed .zip? I'm not familiar with Flashfire yet, so I'm off to educate myself.
thorvindr said:
Just to make sure I understand what you're telling me: even with a locked bootloader, it should be safe to use Flashfire to apply the xposed .zip? I'm not familiar with Flashfire yet, so I'm off to educate myself.
Click to expand...
Click to collapse
Modifying or flashing a custom rom is fine, the bootloader doesn't really care, neither does knox seemingly.
ashyx said:
Modifying or flashing a custom rom is fine, the bootloader doesn't really care, neither does knox seemingly.
Click to expand...
Click to collapse
Having trouble finding documentation on this device's partitions, which are (it seems) not quite the same as most Android devices. To make sure I can recover from (for example) a bad ROM flash, what should I backup? Is flashfire the thing to use for making such a backup?
You can use Flashfire to make a backup, but it's not going to help you in a no boot situation. Be very careful what you flash. Some things such as xposed can leave you in a no boot situation if incorrectly flashed.
My first port of call would have been capturing the ota for backup purposes. Unfortunately that is probably out of the window now you have rooted.
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
ashyx said:
You can use Flashfire to make a backup, but it's not going to help you in a no boot situation. Be very careful what you flash. Some things such as xposed can leave you in a no boot situation if incorrectly flashed.
My first port of call would have been capturing the ota for backup purposes. Unfortunately that is probably out of the window now you have rooted.
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
Click to expand...
Click to collapse
If I can boot to recovery, won't I be able to access the flashfire backup on my microsd card? As long as I don't try to flash a custom recovery, shouldn't I always be able to work from that backup? Or does a flashfire backup need the flashfire app to be useable?
thorvindr said:
Or does a flashfire backup need the flashfire app to be useable?
Click to expand...
Click to collapse
You just answered your own question.
ashyx said:
You just answered your own question.
Click to expand...
Click to collapse
No, I didn't. I assume you're telling me the answer to my first question is no?
ashyx said:
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
Click to expand...
Click to collapse
Anywhere you could point me to figure out how to do that? If I had that, I'd be golden. Hell, I'd share it with the world since for whatever reason nobody seems to have stock ROMs for the 807a.
thorvindr said:
No, I didn't. I assume you're telling me the answer to my first question is no?
Click to expand...
Click to collapse
I quoted your last question. The answer is you need flashfire.
---------- Post added at 07:24 PM ---------- Previous post was at 07:06 PM ----------
thorvindr said:
Anywhere you could point me to figure out how to do that? If I had that, I'd be golden. Hell, I'd share it with the world since for whatever reason nobody seems to have stock ROMs for the 807a.
Click to expand...
Click to collapse
Tbh I don't use kies/smart switch much, but you will find information on it on the net.

Categories

Resources