Related
Phone Details
Motorola Atrix 4G AT&T (bought around June 2011 Time frame)
System Version
4.5.91.MB860.ATT.en.US
Model Number
MB860
Android Version
2.34
Baseband Version
N_01.77.30P
Webtop Version
WT-1.2.0-110
Kernel Version
[email protected] #2
Build Number
4.5.91
I am absolutely new to this Android ROM installs on the phones. Though I decided to install this ROM I absolutely didn’t’ have any idea how to proceed. As a beginner I started doing the following in order.
Download and Keep the CM7 ROM
1. Downloaded Ba2F.zip to my laptop
2. Downloaded and Installed the Motorola USB drivers MotoHelper_2.0.53_Driver_5.2.0.EXE
3. Connect the Atrix and set the USB option on the phone to “USB Mass Storage”
4. Copy both BaTF.zip as well as the Extracted one to Phone internal storage as well as the Ext-SDcard on the phone
Download ROM Manager and Titanium Backup
1. Downloaded both from Android Market (ROM Manager Pro and Titanium Backup Free Version)
2. Both Apps won’t open because I had not ROOTED the phone
Root the Phone
1. I used “Pete's Motorola Root Tools.EXE” file to ROOT the phone
2. Followed step by step as mentioned here http://www.androidauthority.com/how-to-root-motorola-atrix-4g-35233/
Flash ClockworkMod Recovery
1. I used ROM Manager to do this as when you try to do anything in ROM manager it prompts to do this. The version of this is 5.0.2.0 ( I am not sure what is this for why we have to do this)
Unlocking the Bootloader
1. What I learned is, to unlock the bootloader, we have to first flash the phone with the SBF file
a. Installed RSDLite5.3.1.msi
b. Loaded the file 4547-fix-try2.sbf (Downloaded from http://forum.xda-developers.com/showthread.php?t=1136261)
c. Boot the phone with Power+volume UPPER key pressed till "Starting RSD protocol support" comes up
d. Connect to the Laptop and Hit Start button in RSD Lite Program
e. It Did Throw an error saying “FAIL” after showing the following message
i. Failed to boot: error 0x1000'( not word for word). There will also be a list of boot options like Fastboot, RSD, Recovery, etc. And it says Starting Fastboot Protocol
2. Then comes unlocking the phone
a. Though I had the previous error message, it still had the Fastboot Protocol loaded
b. I went to the FASTBOOT folder in command prompt of my laptop executed the following to unlock the phone which worked perfectly as I see the “Unlock” on the left hand corner when phone boots
c. fastboot oem unlock (it gave me the code) then I used the code to unlock
d. fastboot oem unlock #######
e. fastboot reboot
3. Installing the recovery IMG
a. I had downloaded the Recovery IMG file (recovery-atrix5.img) from http://forum.xda-developers.com/showthread.php?t=1204500
b. Booted the phone into Fastboot mode (turn off phone, hold power and volume down key until 'fastboot' appears then use volume up to select so it says 'starting fastboot protocol support').
c. From the CMD promnt and FASTBOOT directory I used fastboot erase recovery
d. Then I executed fastboot flash recovery recovery-atrix5.img (Note: I didn’t rename the file to recovery as suggested by some people)
e. Then gave fastboot reboot to restart.
4. Booting into Recovery mode (This is where I have the problem)
a. The phone is not booting into recovery it’s not going past the Android and yellow Triangle screen
b. I re-flashed the phone same SBF file (this time it was a success showed in the RSD Lite Program), re-installed the same IMG file after renaming to recovery.img
c. Also tried with a different IMG from the same link (recovery-blue-atrix5.img) but no luck
d. Also deleted the file install-recovery.sh from ./etc/ folder (bought the app root manager to delete the file) and then push the recovery.img, no luck
e. Some people said to TAP the bottom right corner while on that screen, did that but nothing is happening
f. Then I saw a note to press both the Volume Keys at the same time, this works but in this mode the cursor (I mean the selection) on the phone doesn’t go to the First TWO (i and iii) shown below, it allows me to select any of the last FOUR (v, vi, vii, viii).
i. Android System Recovery <3e>
ii. <EMPTY LINE >
iii. Android System Recovery utility
iv. <EMPTY LINE >
v. Reboot System now
vi. Apply update from sdcard
vii. Wipe data/factory reset
viii. Wipe cache partition
g. Using the above option I did factory reset but sill no results.
5. Current condition of the phone
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
First of all, I applaud your effort in giving the a very comprehensive description of your issue.
Second, it seems you are having issues with installing a custom recovery because the recovery you're describing is still the stock recovery. I'll look around and see if I can find something that might help.
jhakash said:
4. Booting into Recovery mode (This is where I have the problem)
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
Click to expand...
Click to collapse
---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------
Have you tried re-installing the CWM from RomManager through RomManager? And then boot into recovery from within the app?
---------- Post added at 11:40 AM ---------- Previous post was at 11:31 AM ----------
EDIT: This might seem trivial, but is "USB Debugging" turned on?
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Glad I can help, also, I think it's recommended to use the RomManager recovery for CM7 so good thing it worked.
jhakash said:
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Click to expand...
Click to collapse
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
If you downloaded the CWM zip file for the romracer recovery and as long as RomManager's recovery is working then, yes, you can.
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
ghost_og said:
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
Click to expand...
Click to collapse
live4nyy said:
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
Click to expand...
Click to collapse
Woops, I should have read more carefully. It's best to remove the file first and then flash the recovery.img, or else the script will install the stock recovery on boot. That would make stock recovery the current one on the phone at the time of the script getting deleted.
I would double check and make sure /system/etc does not have install-recovery.sh. If it is not there, then proceed to the fastboot steps and reflash the recovery.img again. It should stick this time.
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
jhakash said:
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
Click to expand...
Click to collapse
I just checked out my girlfriend's stock, locked, unrooted Atrix and she actually has install-recovery.sh in both /etc and /system/etc. Her file manager does not alphabetize anything in either folder, so I almost overlooked the second one.
If you're already on CM7, then you probably won't need to worry anymore. They have an entirely different set of start up scripts in that folder. Welcome to the community!
At this point I do not know enough to help you any further with this issue. All I knew about is the file that needs to be removed that @ghost_og has mentioned. But if you can flash it from RomManager and access CWM from there as well then I guess that's a good enough workaround for now.
Does anyone else have any idea why the stock recovery cannot be removed?
jhakash said:
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
Click to expand...
Click to collapse
I am good to go now, everything seems to be functioning well after flashing CM7 ROM, no more recovery issues, and the Stock recovery is gone now.
Appreciate for all the info you guys provided, it helped a lot. Have a great day and Merry Christmas.
Regards
Jhakash
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
obarthelemy said:
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
Click to expand...
Click to collapse
If you can still use ADB your tablets bootloader is likely not messed up, it sounds like you booted the tablet into fastboot mode not recovery. To get into recovery you can enter it by holding a key combination the most common combination is holding volume up plus the power button at the same time. If that doesn't work from ADB you should be able to get into recovery by running the command:
Code:
adb reboot recovery
Also ROM manger doesn't always work right with every device so I would recommend just uninstalling ROM Manager for now. If it is booting fine into bare ICS then your tablet should be ok, if your looking for Google Apps for ICS they can be found here http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip. Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
obarthelemy said:
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
Click to expand...
Click to collapse
obarthelemy said:
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
Click to expand...
Click to collapse
obarthelemy said:
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
Click to expand...
Click to collapse
The recovery you are referring to is to the standard Android 3e recovery it is included in every version of Android, and will always be like that unless you install a custom recovery such as CWMR and or TWRP. As a general rule you should never install a custom ROM without having a custom recovery image installed first, essentially all the stock 3e recovery is good for is installing OTA updates and preforming a basic factory reset of your phone. You should try and fix your recovery before going any-further, you can sign the un-signed zip by using this tool. Overall, I would focus on trying to fix the recovery to prevent any further damage to your tablet and so that way you have a simple way to recover from anything that might go wrong when flashing ROMs, mods, and other zip files.
issue with the uImage linked
The uImage linked on the download pages for the CM10 and CM9 version ends in ".*"
I have no clue what the normal extension should be; replacing that *.zip doesn't work. Is the file bad, or am I just too clueless about what to do with it ?
Ok so the question is:
1- which "recovery mode" file should I install on my tablet, especially since the mod author's ones seem flaky
2- how do I do that via ADB since my tablet no longer seems to have a working "recovery mode".
I'm sorry to hassle you with those questions... I've looked around, I can't find info nor files I'm confident about ?
Here We have the Root And CWM for Nexus 10 On Android 4.2.2!
Step 1 - Download Android SDK from the Android Developers website and install with USB drivers. See: How to Set Up Android SDK (Fastboot / ADB) on Windows.
Step 2 - Enable USB Debugging mode in your Nexus 10 tablet.
Step 3 - Download Fastboot and extract it in android-sdk-windowsplatform-tools directory. Create directory if not already there.
NOTE: Skip Steps 1, 2, 3 if you already have them.
Step 4 - Download SuperSU v1.04 (UPDATE-SuperSU-v1.04.zip) and copy it to your sdcard on your Nexus 10 tablet.
Step 5 - Make sure you have backup your data as it will be removed. Then switch OFF your Nexus 10.
Step 6 - Download recovery-clockwork-touch-6.0.2.3-manta.img and copy/paste it in the android-sdk-windowsplatform-tools directory.
Step 7 - Now go into Fastboot Mode on Nexus 10. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Step 8 - Navigate to android-sdk-windowsplatform-tools directory and open Command Prompt (Shift + Right-click > Open Command Prompt).
Step 9 - Type in the following command and press Enter.
fastboot flash recovery recovery-clockwork-touch-6.0.2.3-manta.img
Click to expand...
Click to collapse
Step 10 - Once completed, choose RECOVERY MODE from the Fastboot menu and enter Recovery Mode.
Step 11 - Then scroll down to “flash zip from SD card” and press the Power button to select it.
Step 12 - Press the Power button again and select “choose zip from sdcard”.
Step 13 - Now using your volume keys, navigate to the UPDATE-SuperSU-v1.04.zip file that you copied to your SD card and select it using the Power button. Confirm the installation on the next screen and the installation procedure should start now.
Step 14 - After the installation completes, go to “+++++Go Back” and reboot the phone by selecting “reboot system now” from the recovery menu. Then Choose yes flash recovery back (this will make CWM your permanent recovery mode)
That’s it. Your Nexus 10 is now rooted on Android 4.2.2 JDQ39 software version of Jelly Bean and even has a custom CWM recovery installed. Check for the SuperSU app in your apps list to verify.
Root and CWM for Nexus 7
Root and CWM for Nexus 4
Reserved...
Thanks udi, but could you also post how to do it on stock rom with stock recovery? Much appreciated! I keep wathing your youtube videos lol :good:
lKBZl said:
Thanks udi, but could you also post how to do it on stock rom with stock recovery? Much appreciated! I keep wathing your youtube videos lol :good:
Click to expand...
Click to collapse
what do u want root or recovery??
AW: [How-to]Root Android 4.2.2 And Install CWM
lKBZl said:
Thanks udi, but could you also post how to do it on stock rom with stock recovery? Much appreciated! I keep wathing your youtube videos lol :good:
Click to expand...
Click to collapse
I think you have to unlock your device first. Then you can easily install your custom recovery
how do I install TWRP now?
never mind was trying to flash a .TAR file this wayyy... figured it out. need a .img
Use the nexus 10 toolkit
Side Load via adb,
then re run the everything script in toolkit.
Worked like a charm for me, however, I did have to reflash back to my first backup, to be on stock 4.2.1 with stock kernel
mrdunlop said:
Use the nexus 10 toolkit
Side Load via adb,
then re run the everything script in toolkit.
Worked like a charm for me, however, I did have to reflash back to my first backup, to be on stock 4.2.1 with stock kernel
Click to expand...
Click to collapse
did it work for 4.2.2 ? i was rooted with 4.2.1 but the OTA screw it up.. i have to recover to factory .. then OTA ｔｏ ４．２．２
ｃｏｕｌｄ ｙｏｕ ｐｌｅａｓｅ ｂｅ ｍｏｒｅ ｓｐｅｃｉｆｉｃ ？
followed this method last night and got my tablet rooted with TWRP's recovery!
epunk said:
followed this method last night and got my tablet rooted with TWRP's recovery!
Click to expand...
Click to collapse
Glad that It's working!
Download Fastboot?
I cant download Download Fastboot... I have been denied access??? little help over here please I wanna root my device on 4.2.2... Thanks in advance!
just did the same thing with my n7, worked out easily on my mac !
#1 thanks a lot dude
Mr_Jay_jay said:
I cant download Download Fastboot... I have been denied access??? little help over here please I wanna root my device on 4.2.2... Thanks in advance!
Click to expand...
Click to collapse
http://www.mediafire.com/?lt8ghch95u5abgo fastboot files!
hope this one works :fingers-crossed:
I followed your method and got:
1.- Clockworkmod E:can't mount /sdcard/
2.- System stuck at Nexus X logo
What do I do now?
[update]
1.- Got factory image: https://developers.google.com/android/nexus/images#mantaray
2.- Ran "flash-all.bat" from the tgz
3.- Flashed recovery-twrp-2.4.2.0-manta.img
4.- TWRP asked if I wanted to install SU, I said yes
5.- Happy days.
Sorry if this has already been asked and I'm not understanding it.
I bought my mom a Nexus10 and it's missing some Indian fonts on it. I saw I need to flash on a fontpack to add them.
The tablet is totally stock, on 4.2.2..
Do I need to unlock the bootloader first (which wipes all the data) and then do the steps from the 1st post?
This whole process is not working for me. I am in windows 8 and it just doesnt let me install sdk nor even ask me to install drivers. Can you suggest what is the possible way out? I am unable to move ahead due to these issues :/
Root failed.
I followed all instructions (I have successfully rooted a number of smartphones and the Nexus 7 before this). The end result is that the Nexus 10 is unlocked, but hangs on bootup with just the X showing. I can't go into Recovery mode (I just get the Android lying on his back with an exclamation point showing and eventually it tries a normal boot - as far as the X).
I can't try Restart Bootloader as this, too, leads to just the X and hangs. I have reset the tab (power + down volume) and also have tried to reconnect the tab to the PC, which now does not recognize it, putting fastboot.exe and adb.exe out of reach. I think something might have gone wrong installing CWM, though it did boot up a couple of times after that with a couple of errors that passed by too fast to copy - before it started to hang. I never got a chance to put superuser on it as Recovery mode is out of reach. I tried a master reset the last time I got to Recovery Mode, but got several minor errors and now seem not to have ANY bootloader working. Short of sending the tab back to Google to have them restore a 'cherry' Android 4.2.2 (for a sum), I'm lost as to where to go next.
Any ideas?
s
paano po mag rooted ng myphone Rio fun
My recovery is lost when I did this!!!
I did this with adb....almost same step......now when try to go to recovery mode.....just logo......! I have to take battery out! so that I could boot into android.......when I accidently type -w which was for wipe,,,,,,,wiped thw whole phone..... now its just white screen when i boot into android......cant install new rom because recovery is lost.......what should I do now? help me please!
how to root s3mini 8200
Just some things before we start. My Phone is the P769 and I'm a total noob.
Alright, I rooted my phone yesterday and then proceeded to download CWM, the app of course. So, when I went to setup a custom recovery, I picked from the options they had their, to which I picked the P760. Low and behold, I found it was a horrible failure when I rebooted into recovery because I got the security error...I think I soft-bricked it? Correct me if I'm wrong. Anyways, I just downloaded the LGSupport Tool and eventually fixed it.
So I think my question is, where can I get a custom recovery for the P769? Am I supposed to be looking for that in the first place? As you can see, I'm quite lost.
Is your bootloader unlocked?
Sent from my LG-P769 using XDA Free mobile app
BlueKnightedDragon said:
Is your bootloader unlocked?
Sent from my LG-P769 using XDA Free mobile app
Click to expand...
Click to collapse
Um...I want to say no.
Do you want custom recovery to flash themed stock roms or custom rom (like cm 11) cause for the latter you need to unlock bootloader first
Sent from my LG-P769 using XDA Free mobile app
BlueKnightedDragon said:
Do you want custom recovery to flash themed stock roms or custom rom (like cm 11) cause for the latter you need to unlock bootloader first
Sent from my LG-P769 using XDA Free mobile app
Click to expand...
Click to collapse
I have the cm 11 rom file and the gapps file. I just can't find the correct recovery on Rom manager to reboot into so I can install the files
You will first have to unlock your boot loader in that case, follow all the instructions from the first ONLY: http://forum.xda-developers.com/showthread.php?t=2601480
Then, do the follwong:
1. Have one of the recoveries from here: http://forum.xda-developers.com/optimus-l9/development/p769-recoveries-p769-mirror-issues-t2879854, CM11 and the required G.Apps on your SD card.
2. Navigate (use a mirror if needed) through cwm, restore your choice of #1, and reboot into recovery again from the cwm (Under "advanced")
3. The new recovery should look different and not be mirrored, but the touch will be wonky, don't worry. Flash the CM11 and G.Apps. Do NOT reboot yet.
4. Then flash "cwm_ts_fix_p769.zip". reboot
Done!
I might get to writing a guide after my experience doing the exact same and getting my head around it for the past 2-3 days, but I have a very busy schedule, so I cna't promise anything. Besides, kuma82's guide is excellent.
mohitgarg said:
You will first have to unlock your boot loader in that case, follow all the instructions from the first ONLY: http://forum.xda-developers.com/showthread.php?t=2601480
Then, do the follwong:
1. Have one of the recoveries from here: http://forum.xda-developers.com/optimus-l9/development/p769-recoveries-p769-mirror-issues-t2879854, CM11 and the required G.Apps on your SD card.
2. Navigate (use a mirror if needed) through cwm, restore your choice of #1, and reboot into recovery again from the cwm (Under "advanced")
3. The new recovery should look different and not be mirrored, but the touch will be wonky, don't worry. Flash the CM11 and G.Apps. Do NOT reboot yet.
4. Then flash "cwm_ts_fix_p769.zip". reboot
Done!
I might get to writing a guide after my experience doing the exact same and getting my head around it for the past 2-3 days, but I have a very busy schedule, so I cna't promise anything. Besides, kuma82's guide is excellent.
Click to expand...
Click to collapse
Thank you soooo much. But unfortunately, I have one more question. How do I perform an offline flash?
Here you go: http://forum.xda-developers.com/showthread.php?t=2085344
mohitgarg said:
You will first have to unlock your boot loader in that case, follow all the instructions from the first ONLY: http://forum.xda-developers.com/showthread.php?t=2601480
2. Navigate (use a mirror if needed) through cwm, restore your choice of #1, and reboot into recovery again from the cwm (Under "advanced")
Click to expand...
Click to collapse
First off, thank you sooo much. I got this far but right now I'm super confused. How do I restore? Is there an option to restore? Can you explain it to me a bit more specifically if you can?
Also, I didn't know I needed a literal mirror lol.
Ownage516 said:
First off, thank you sooo much. I got this far but right now I'm super confused. How do I restore? Is there an option to restore? Can you explain it to me a bit more specifically if you can?
Also, I didn't know I needed a literal mirror lol.
Click to expand...
Click to collapse
Sorry for the vague instructions, first, let me ask, is your phone successfully unlocked? Got that fastboot menu on the phone somewhere along the process? Or you can try connect in SW DL mode (Power off phone, hold Vol+ and plug in USB, should see "Unlocked bootloader").
If yes, then you should be on the European 20B with mirror screen and wonky touchscreen, follow the below instructions:
1. Have one of the recoveries from the link I posted AND CM11 (I am using dhiru's version) AND G.Apps AND cwm_ts_fix_p769.zip on to your external SD.
2. Run Start.cmd, push files (Fix_Touch-V20F.zip & MetroPCS-V10E-Radio.zip) to External SD using kuma82's tool
3. Install BusyBox and reboot into the inverted CWM recovery
4. Navigate (use a mirror if needed) through CWM, flash the recovery of your choice AND choose to reboot to recovery from within the recovery
5. (CWM should not be inverted now). Install the files in the given order without a reboot in between:
a. CM11
b. G.Apps
c. Fix_Touch-V20F.zip
d. Recovery you flashed in step 4 - This is critical, as Fix_Touch-V20F.zip installs an older recovery which may cause soft-brick, thus you need to install the recovery again
e. cwm_ts_fix_p769.zip[/INDENT]
6. Reboot
mohitgarg said:
Sorry for the vague instructions, first, let me ask, is your phone successfully unlocked? Got that fastboot menu on the phone somewhere along the process? Or you can try connect in SW DL mode (Power off phone, hold Vol+ and plug in USB, should see "Unlocked bootloader").
If yes, then you should be on the European 20B with mirror screen and wonky touchscreen, follow the below instructions:
1. Have one of the recoveries from the link I posted AND CM11 (I am using dhiru's version) AND G.Apps AND cwm_ts_fix_p769.zip on to your external SD.
2. Run Start.cmd, push files (Fix_Touch-V20F.zip & MetroPCS-V10E-Radio.zip) to External SD using kuma82's tool
3. Install BusyBox and reboot into the inverted CWM recovery
4. Navigate (use a mirror if needed) through CWM, flash the recovery of your choice AND choose to reboot to recovery from within the recovery
5. (CWM should not be inverted now). Install the files in the given order without a reboot in between:
a. CM11
b. G.Apps
c. Fix_Touch-V20F.zip
d. Recovery you flashed in step 4 - This is critical, as Fix_Touch-V20F.zip installs an older recovery which may cause soft-brick, thus you need to install the recovery again
e. cwm_ts_fix_p769.zip[/INDENT]
6. Reboot
Click to expand...
Click to collapse
Alright, I kinda softbricked on step 4. I believe my bootloader is unlocked since I'm in CWM, right? I'm going to start from the top again, but I have a bit more confidence this time around.
On step 4 of flashed "CWM 6.0.4.8 No-Touch for P769" and then rebooted in recovery, the option under advance and got a secruity error, or a soft brick...same thing I believe. I dunno what I did wrong.
Check if your are unlocked, try going into software download mode.
Alright, when I go into SW DL, it doesn't say unlocked bootloader, it just shows what it normally shows. But I have the mirror screen and wonky touchscreen...did I miss a step or something? I did everything I believe.
Ownage516 said:
Alright, when I go into SW DL, it doesn't say unlocked bootloader, it just shows what it normally shows. But I have the mirror screen and wonky touchscreen...did I miss a step or something? I did everything I believe.
Click to expand...
Click to collapse
There are steps missing after step 3 you need to flash radio in the inverted recovery and then reboot and the tool and run the unlock command after 45 minutes and press vol + to unlock and then flash a recovery while you're phone is still in fastboot mode (this is the mode your phone is in after you press the vol + to unlock) by using the command fastboot flash recovery (insertrecoveryname).img
Alright, after I push both files to the sd card, I try to install the radio zip, but it fails. Does the problem lie there in?
Wait, did you follow everything from the first post in this thread as I mentioned earlier: http://forum.xda-developers.com/showthread.php?t=2601480
If yes, then what happened after step 8?
Once you do that, THEN you have to do what is outlined in this post: http://forum.xda-developers.com/optimus-l9/general/noob-little-guidance-t2878048/post55588776
mohitgarg said:
Wait, did you follow everything from the first post in this thread as I mentioned earlier: http://forum.xda-developers.com/showthread.php?t=2601480
If yes, then what happened after step 8?
Once you do that, THEN you have to do what is outlined in this post: http://forum.xda-developers.com/optimus-l9/general/noob-little-guidance-t2878048/post55588776
Click to expand...
Click to collapse
Is there honestly something that should be different? Because, when I press the option to unlock the bootloader, it just reboots and what...almost identical with the results of step 6.
Am I playing with my phone wrong? What am I really supposed to do to it for 45 minutes...I want to say there in lies my problem.
Excuse me as I head to class with super inverted phone, lol.
Yes, you have to wait about 45 mins as mentioned in the step, that is why we said follow it to the T.
TWRP has been successfully ported to the Galaxy J7 Refine (SM-J737P) (Oreo 8.0)ROOT METHOD POSTED BELOW IN POST #2Giving credit where credit is due:
@Dark98 for compiling the TWRP.img
@☆KØŁØЯΛĐØ☆ providing device files + testing/porting
@topjohnwu for Magisk
DISCLAIMER: This is NOT in Odin flashable .tar format. Due to sporadic updates in security & Oreo, Odin won't be much help here.
This has been tested & confirmed working on device build R16NW.J737PVPU1ARG3. It should work on other versions.
UPDATE: This will work on any Oreo version as well, including the new April 1, 2019 R16NW.J737PVPS3ASC2 update.
The patched_boot.img.tar I've attached will not work if you are on a different version of Oreo. You must provide your own patched_boot.img.tar that coincides with your respective version.
Proof of port is in the screenshot below (I've underlined the device build)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There is a downside & an upside:
- The downside is that after you flash TWRP & reboot, you will lose root.
- The upside is that TWRP will remain so all you need to do to regain root is flash the Magisk-v18.1.zip in Recovery.
Procedure:
- In order to flash, you need an app that will do so without booting into recovery. View attachment Flashify.apk is the ideal choice for this procedure.
- Flash TWRP in Flashify but do not reboot from the app itself. Power off your device & boot into [TWRP] Recovery manually.
PAY ATTENTION TO THESE NEXT FEW STEPS!!!
- Extract the twrp.img from View attachment J737P_TWRP.zip
- Flash through Flashify, then boot into TWRP for the first time
- Now that you have booted into TWRP the first time, Swipe to allow modifications
- Navigate to Wipe > Format Data > type yes when prompted (this will not delete any files you have in your Internal Storage)
- Once the format is completed, go to TWRP home screen & Reboot > Power Off
DO NOT REBOOT TO SYSTEM
- Once device powers off, reboot back into TWRP (yes you will boot into recovery twice)
If you fail to immediately boot back into TWRP, you will brick & have to start over. The fiirst reboot is to clear out (wipe) the /Data partition to make room for your new recovery. Wiping will not delete any internal storage items. However, it will return a value of 0 for /Data. The second boot is to secure TWRP as your new Recovery, as well as fix the /Data return value.
- Now that you have secured TWRP, go ahead & make a TWRP backup as a safety precaution before you reboot. The backup could be considered "stock" with TWRP as the Recovery. The reason being is that you will lose root after formatting /Data. No worries, you will get it back.
After creating the backup, follow these next steps very carefully!!
You will now flash Magisk-v18.1 to regain root. With the new security measures Samsung put in late 2017, you will need to flash 2 .zip files after to ensure that root sticks.
YOU NEED TO FLASH THESE FILES IN ORDER. DO NOT WIPE CACHE AFTER EACH FLASH. DO NOT REBOOT AFTER EACH FLASH. FLASH EACH PACKAGE ONE AT A TIME. WAIT UNTIL THE 3RD FLASH IS COMPLETE & THEN REBOOT DEVICE. IT WILL TAKE SEVERAL MINUTES SO BE PATIENT.
(Still in TWRP)
- Go to Home & select Instal
- In this order, flash one at a time:
View attachment Magisk-v18.1(18100).zip
View attachment no-verity-opt-encrypt-6.0.zip
View attachment RMM-State_Bypass_Mesa_v2.zip
DO NOT WIPE THE CACHE
Screenshots of proper installation (in order):
- Reboot device normally. If you do not flash the dm-verity & RMM .zip files in order, you will bootloop & have to start over.
- When you get to your home screen, you will receive a notification to update Magisk. Update by either selecting the notification or manually through Magisk Manager.
- Allow Magisk to install the update; do not update through TWRP.
ĐØΠΞ
[ROOT] Galaxy J7 Refine (SM-J737P) (Oreo 8.0)
FOLLOW THESE DIRECTIONS. I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE.
View attachment 4733553 View attachment 4733552
I have given you a freebie by providing the patched_boot.img.tar, thus saving you a few steps
All files needed are uploaded to my Drive: https://drive.google.com/folderview?id=1-8CGkYef58I-DrkyOshRFniecO_0dBDc
NOTICE: Patched_boot.img.tar is solely for the J737PVPU1ARG3 software version. Any attempt to flash to a different version will result in a bootloop. You must patch + flash your own stock boot.img if you are on a different software version.
YOU MUST PAY ATTENTION TO THE FOLLOWING
- In the Bli5zkrieg.zip you extracted, load up Odin_v13.1 (non-patched)
- Load only the BL/AP/CP files from your stock firmware into Odin
- As soon as the flashing process ends, you must reboot quickly back into Download Mode. You have to be quick. If you allow the device to begin booting up, it makes the rooting process more difficult.
Assuming you followed directions...
- Close Odin_v13.1 & unplug your device while still remaining in Download Mode
- Launch Odin_v13.1 [Patched] & load up the patched_boot.img.tar in the AP slot
- Reconnect device & proceed to flash
- Device will reboot with "Verification Failure" so you must reset (this is part of root) (it does not activate FRP lock)
- When device reboots to Setup Wizard, skip through it. Do not add any accounts (Google or Samsung). Do not consent to giving any device data for whatever purposes (they will ask twice; look carefully)
- On the home screen, unlock Dev Options &allow USB Debugging. OEM should already have been unlocked
- Connect device to your pc & in the ZeeToolz folder you extracted, run CMD.exe
- Input adb devices to ensure proper connection
- Input adb install -r MagiskManager-v7.0.0.apk to install MM to your device
- Open MagiskManager & make sure everything is good to go (see attached screenshot)
- If everything is done properly then you will see a superuser tab in the left side-bar, indicating root access
ĐØΠΞ
Thanks for making / working on this man. Running butter smooth on my SM-j737P (J737PVPU2ARJ2.)
note: I had to use an sdcard to store the proper files to be able to flash in twrp. adb sideload nor mtp would not work while in twrp during the initial install.
I used the files below.
Root Files (patched boot image): https://drive.google.com/file/d/1xan3RfRs4x4As7ONxLtW-WXKh_KvjyXY/view
Unbrick Files (stock J737PVPU2ARJ2) : https://androidfilehost.com/?fid=11410932744536992025
Cheers!
kinehumane said:
Thanks for making / working on this man. Running butter smooth on my SM-j737P (J737PVPU2ARJ2.)
note: I had to use an sdcard to store the proper files to be able to flash in twrp. adb sideload nor mtp would not work while in twrp during the initial install.
I used the files below.
Root Files (patched boot image): https://drive.google.com/file/d/1xan3RfRs4x4As7ONxLtW-WXKh_KvjyXY/view
Unbrick Files (stock J737PVPU2ARJ2) : https://androidfilehost.com/?fid=11410932744536992025
Cheers!
Click to expand...
Click to collapse
No problem man. I didnt think to test sideload or mtp as I always use an SDcard (comes in handy lol). It was a tad bit tedious to get the whole process down due to Oreo. That being said, ensure that you have a backup. Editing any part of the system (ie. Build.prop) will result in failure. I installed the Time Zones update & it failed. As far as MagiskSU goes, I like the Modules but prefer SuperSU root. Will see about incorporating it in the near future
This is likely a silly question, but I downloaded and installed flashify, have put the TWRP.img on the SD Card, but for some reason, flashify won't go further than giving me the option of flashing a recovery... one tap and the app is frozen....
So, is there another app that will flash the image, so as to follow the directions in the OP? Flashify doesn't seem to be happening for me. Can't seem to find one that doesn't do a root-check first, refusing to do the deed if root isn't there yet?
Trying from square 1, to the point that I did a total backup, factory reset, and am starting with a reset phone.
pauljulian said:
This is likely a silly question, but I downloaded and installed flashify, have put the TWRP.img on the SD Card, but for some reason, flashify won't go further than giving me the option of flashing a recovery... one tap and the app is frozen....
So, is there another app that will flash the image, so as to follow the directions in the OP? Flashify doesn't seem to be happening for me.
Click to expand...
Click to collapse
I experienced the sluggish behavior as well. Manually go into Magisk Manager > SuperSU & make sure Flashify has been granted root access. I've noticed Magisk is rather slow when it comes to asking or granting root access on some apps. If you cannot get it to flash with Flashify, I'd suggest going with Root Essentials. Its an all-in-one root toolbox with a flashing mechanism
Root Essentials won't work as a secondary flasher bc it requires a custom recovery to be installed beforehand. Flashify will be your best bet so try all possibilities to get it to work
☆KØŁØЯΛĐØ☆ said:
I experienced the sluggish behavior as well. Manually go into Magisk Manager > SuperSU & make sure Flashify has been granted root access. I've noticed Magisk is rather slow when it comes to asking or granting root access on some apps. If you cannot get it to flash with Flashify, I'd suggest going with Root Essentials. Its an all-in-one root toolbox with a flashing mechanism
Click to expand...
Click to collapse
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
pauljulian said:
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
Click to expand...
Click to collapse
I revised my last comment. TWRP is to be flashed after you have rooted with Magisk. The posts are a little offputting due to the order they are in & I apologize for that lol Root with Magisk first & then you can install TWRP
pauljulian said:
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
Click to expand...
Click to collapse
Hmm... Root Essentials tells me it failed to install the image...
If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
☆KØŁØЯΛĐØ☆ said:
I revised my last comment. TWRP is to be flashed after you have rooted with Magisk. The posts are a little offputting due to the order they are in & I apologize for that lol Root with Magisk first & then you can install TWRP
Click to expand...
Click to collapse
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
pauljulian said:
Hmm... Root Essentials tells me it failed to install the image...
If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
Click to expand...
Click to collapse
Flashing with Flashify is under the assumption that you dont have a lot of 3rd party apps installed. If you are logged into your Google or Samsung account(s) & have your data being backed up, it creates a more sluggish environment.
First, follow the rooting guide I posted above. If you do, you should have root access via Magisk with very little apps installed & you arent logged into any Account(s). After you have that, then install Flashify. Manually set root access if need be. Make sure you have all your device security settings disabled, Dev Options, USB Debugging, blah blah blah
We will get you root access & TWRP installed bud
pauljulian said:
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
Click to expand...
Click to collapse
When you go to get root, you will need your stock firmware (BL/AP/CP files). My directions are pretty straight forward. Unzip the tools, load up Odin (non-patched), flash BL + AP + CP in their respective slots. Make sure that after you flash the stock, you instantly reboot back into Download Mode. Close the current Odin & open the patched Odin. Load the patched_boot.img.tar I provided to the AP slot & flash. It will reboot with a Verification Failure, thus forcing you to format your device. When your device reboots, skip through Setup Wizard, dont link any Google or Samsung accts. On the home screen, use cmd terminal on your pc to install the MagiskManager.apk. Once sideload, you will see root access & more than likely a toast notification asking you to update Magisk.
Rashr (View attachment de.mkrtchyan.recoverytools.apk) works as a good substitute for Flashify. You just need to move the TWRP.img to the root of your sdcard (/emulated/0/sdcard) & flash it through the Recovery from Storage option. Reboot into TWRP &continue following the instructions I've posted
pauljulian said:
Hmm... Root Essentials tells me it failed to install the image...
If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
Click to expand...
Click to collapse
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
Click to expand...
Click to collapse
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...
pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...
Click to expand...
Click to collapse
Lol The directions are on point. They're solid. You just have to pay attention ?
Here's the old fart with another question....
After flashing the stock files as instructed, I immediately hit the download mode as soon as the screen went black. Flashed the patched boot as instructed, and, as you stated, it would go immediately into recovery due to verification error.
I wiped the cache and hit factory reset, then reboot.
It's now sitting at the boot logo screen, and has been there for more than 1/2 hour.
Honest! I followed your instructions to the letter, and I recall first boot after rooting taking a while to come up into the system on other devices I've had, but I don't recall first boot taking anywhere this long.
I'm stumped.
pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...
Click to expand...
Click to collapse
pauljulian said:
Here's the old fart with another question....
After following the instructions, yes, the phone went immediately into recovery mode, after flashing the error message you described.
I went ahead and did the factory reset, and told it to reboot... It's been sitting at the boot logo for about 25 minutes.
Should it take this long for first boot, after flashing the patched.boot.img.tar? I loaded the tar into the AP slot, as instructed. After flashing it, and the screen going to black, hit the download mode immediately... I flashed it, as said, at reboot, it went into recovery after a quick error message... I did factory reset, then rebooted normally.
I really have no idea... I'll let it keep sitting, to see if it finally boots, but this seems like a terribly long time that it's' at the bootscreen.
Click to expand...
Click to collapse
You seem to be rebooting into Recovery an awful lot. You shouldn't be booting into recovery mode at all when attempting to root. Recovery mode only needs entered during either process whenever you attempt to flash TWRP. Luckily for you, I dont have sh¡t to do tonight so I can help you until you get it right lol Shoot me an email at [email protected] & we can get started. I dont want to clutter up this feed with a revised how-to guide lol
Other Variants
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
fsceo said:
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
Click to expand...
Click to collapse
I have since revised my instructions for root, starting that my guide is very device specific & you will have to tweak instructions in order to accommodate your version.
As far as TWRP goes, did you boot into TWRP twice? Once for the initial install to format the /data partition & the second to secure TWRP along with flashing the files? You need to do it simultaneously & in order otherwise it won't work
It's a happenin' thang!!!!
Many thanks to Killer for all the help! Decent person stayed up with me troubleshooting until 6:30 this morning... It's working!!!!
(now, if I can find the damned SIM card that bounced off my desk into the carpeting, I'll have basically a laptop replacement! (well, for a lot of things, that is... <chuckle>)
pauljulian said:
It's a happenin' thang!!!!
Many thanks to Killer for all the help! Decent person stayed up with me troubleshooting until 6:30 this morning... It's working!!!!
(now, if I can find the damned SIM card that bounced off my desk into the carpeting, I'll have basically a laptop replacement! (well, for a lot of things, that is... <chuckle>)
Click to expand...
Click to collapse
Not a problem buddy. Was fun & if you have any more questions, you have my contact info
fsceo said:
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
Click to expand...
Click to collapse
Sent you a pm, but having trouble rooting the same variant