Odin/ TWRP - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

I'm having a hard time flashing TWRP using Odin I'm using the latest build of Odin and everything works fine until I select TWRP by clicking AP after that Odin freezes and does not respond ....is there any fix for this and is there a alternative way to get TRWP without Odin?

It should freeze for a little bit, and then when it has finished checking the file allow for flashing.

How long does that usually take...I've left it for 15mins once

I had to root first then use twrp app on Google play to get it installed

What are your cpu specs? Odin is verifying the files checksum when loaded. A large 1.5gb file will take 1-3 minutes for most folks.
Intel Core i3 4150 @ 3.50GHz
8.00GB DDR3
1TB SSD Storage

Are you running odin as an administrator? If not this could be your problem.

Do you have the latest Samsung smartphone driver installed?
http://developer.samsung.com/technical-doc/view.do?v=T000000117#none

I got it working thanks

Related

[ROM] STOCK - FULL ICS IMM76D.LP10 for Verizon i815 LTE Tab (only!) *UPDATE 10/16*

UPDATE: My hosting I had for XDA related work expired, so I re-uploaded everything here: http://www.mods4cars.com/pub/xda
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ROM Choices:
Original Cloned ROM (First version with direct partition image copy, requires >1GB space on SD card which has caused issues for some)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Update 10/12:
NEW ROM with full ext4 optimizations. System, Cache and Data (only in wipe version) will be cleared, formatted and "fsck -Dfy" checked!
DO NOT WIPE ANYTHING IN CWM!!! Just choose the ROM file appropriately.
Non-Wipe Version (This one leaves existing data partition alone, only checks it for errors)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_nowipe.zip
Wipe Version (THIS ONE WILL FORMAT DATA PARTITION, ALL USER DATA WILL BE LOST!)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_wipe.zip
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
WARNING: DO NOT wipe or factory reset in CWM! You can simply install ICS over an existing Honeycomb setup! Choose the correct ROM version: One erases everything and the other one preserves user data. Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there! We had too many reports of problems when wiping/factory resetting with CWM. So for now the best advice for anyone looking into installing the ROM is DO NOT WIPE!
UPDATED PROCEDURE as of 10/16 - NO NEED to flash the old 3e recovery any more! Much easier and quicker baseband update below...
Step 5: Download and flash the baseband modem.bin with ODIN
Download the baseband update: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Bring the tab back into ODIN mode the same as before. Extract the modem.bin file from the modem.zip and drop it in the PHONE section (not PDA!) in ODIN this time. Click start and let it flash and reboot. Done. Under settings/about device you should now have Baseband Version i815.04 V.LP10 / I815LP10
B]Step 6: Optional: Keep CWM or go all stock[/B]
If you would rather like to be full stock than keeping CWM as the recovery program, then bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash LP10_recovery.
The ROM is pre-rooted. SuperSU is pre-installed as part of the ROM.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium
johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
Yes the 6.0.1.1 (as far as I know!) is safe. No need to wipe anyway. The v2 included more files that turned out to be not necessary. The files posted here along with the updated, safer method of flashing, should be the best and quickest way to get to full stock ICS.
The v2 was mainly an attempt to bring user ice's tab back to life after his data partition got killed.
Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney
Thank you so much, and I do plan on doing a wipe to clear out my Tab to bring it to a clean slate. Just didn't want it to be a broken state lol.
rhester72 said:
Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney
Click to expand...
Click to collapse
IMEI and such is stored in the mmcblk0p1 partition which (along with 2 and 3 which are the bootloader) we don't touch. So no, we only flash the factory fs, lte modem and kernel. CDMA modem.bin via the new method.
electron73 said:
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ICS ROM: http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Modem Upgrade: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Make sure you have MORE than 1GB of free space left on the SD card when done.
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
BTW there is NO NEED to wipe! You can simply install ICS over an existing Honeycomb setup! Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there!
Step 5: Flash the old Honeycomb recovery in order to do the modem upgrade
Since CWM does not understand the proprietary command used to flash the "firmware" which is the base modem file, we need to use STOCK recovery for this. The downside is that, of course, the new recovery is now locked down and won't accept unsigned files. So we need to flash the OLD Honeycomb FD01 recovery and feed it the modem update!
When the CWM flash above is finished and tells you to reboot, simple press and hold power and vol down again to get back into ODIN mode. Connect the USB again and this time use Odin the same way as above, but to flash the FD10_recovery.tar. This time uncheck the "reboot" tick mark.
Step 6: Flash the modem upgrade with the old stock 3e recovery
When Odin is done above, hold down pwr and vol up until you see the old school recovery pop up saying *manual mode*. Select flash update zip from sdcard and select the electron_ICS-LP10_i815_modem.zip this time. It will go on for a while in total bling flight. No output apart from rotating gears! This one is tricky. Just wait until it either ends saying that it is done or a yellow exclamation point shows up in the middle of the screen. The flash is done.
Step 7: Choose between Stock and CWM
Now bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash either CWM or LP10_recovery if you rather like to be full stock. If you chose CWM then be aware that the ROM will try to overwrite that immediately on first boot!! In order to avoid that, flash it with "reboot" box unticked and manually reset into CWM mode (pwr + vol up) and inside CWM select reboot system. It will then give you a big warning that the ROM has a CWM killer and offers you to disable that, so CWM will stay in place (good for Nandroids etd).
Step 8: Boot the ICS ROM and enjoy!
Once you see ICS, go to the play store and install SuperSU. The rom is pre-rooted and just needs the SuperSU app for full root access control.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated
Click to expand...
Click to collapse
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium
bathanr said:
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Same here, what steps do I take to flash the updated modem
Awesome!
ice0901 said:
Same here, what steps do I take to flash the updated modem
Click to expand...
Click to collapse
from step 5 on forward. no need to reflash the whole rom if you already have ICS running.
Just odin the old recovery on, flash the modem update zip, then odin the new recovery or CWM back.
boot loop
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?
rspong said:
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?
Click to expand...
Click to collapse
Weird. OK did the v2 flash go all the way through? Did it finish at some point and say "please reboot" ? Or did it get stuck half way though?
Can you in CWM mount your internal storage? Did you get any errors when you did the full wipe/factory reset? anything saying "error mounting /data" maybe ?
electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)
I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?
almus said:
electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)
Click to expand...
Click to collapse
No I didn't create it but it is guaranteed the right one for i815. I know because I messed up my partition table last night and had to use that pit to repartition Lucky I found that. What you would do in order to re-do your pit is open odin, put the CWM in the PDA section as usual and then click PIT and select that pit. That should activate a checkbox "repartition device". Leave that on for this one run and click start.
As a result it should partition, then flash the CWM and you should immediately be able to enter CWM. With CWM running connect USB
and use adb shell to get onto your tab.
IN the root prompt enter parted /dev/block/mmcblk0
and in the parted prompt enter print. If you see the result as in the attached pic (note: no file system in the DATAFS line) then you need to fix that the same way ice got it fixed last night. I think the link to the thread is in the OP
bathanr said:
I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?
Click to expand...
Click to collapse
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c
Yes. V2 went through with no problems.in CWM I can mount efs,cache,system but not data. Then in cwm... OK..wiping data then I get a error mounting data. Skipping format
Sent from my DROID RAZR using xda premium
chefdave12118 said:
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium
Click to expand...
Click to collapse
The flash controller in our tablets is buggy. See here http://forum.xda-developers.com/showthread.php?t=1862294
electron73 said:
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c
Click to expand...
Click to collapse
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
---------- Post added at 09:43 PM ---------- Previous post was at 08:46 PM ----------
bathanr said:
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
Click to expand...
Click to collapse
I ran into the splash screen just hanging and followed the data retore steps. I keep getting this error when trying to print the print command from the parted prompt.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Flatlinz>f:
F:\>cd 7.7
F:\7.7>cd adb
F:\7.7\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ls
ls
boot init sys
cache init.rc system
charger lpm.rc tmp
data preload ueventd.goldfish.rc
default.prop proc ueventd.rc
dev recovery ueventd.smdk4210.rc
efs res vendor
etc sbin
external_sd sdcard
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Can't have the end before the start!
(parted)
Any ideas?

[Q] Think I deleted the file system from my phone

Before flashing a new rom, I tried formatting /data and /system manually, via recovery. I also tried (because I'm smart that way) to format the file system drive via a nice little tool called diskwipe, which succeeded. Ever since then, i think I don't have a hard drive anymore on my phone, because it seems the roms I've tried to install are being placed on the sdcard. Windows won't recognize it either (it sees the sdcard).
In linux, it shows me that the filesystem is active, just separate from the phone's memory, which can't be accessed. Also, the /mnt folder is empty.
Roms install fine, just without any access to google play or the beginning step-by-step google registration process and so on. I don't have anything on the phone I can't do without, so any help would be vastly appreciated, because it seems I turned a smartphone into an old Nokia :good:
Thanks!
m
Could you connect your phone still to your pc and does Odin detect it in download mode?
Think then you can try to Restock with repartition selected and do so a clean new flash of the rom of your choice....
rodman01 said:
Could you connect your phone still to your pc and does Odin detect it in download mode?
Think then you can try to Restock with repartition selected and do so a clean new flash of the rom of your choice....
Click to expand...
Click to collapse
yep, works, thanks! my question is how to use it with only one zip file, when odin requests all those separate files. i have the ops file, but where do i put the rom zip? I know there's the one package option, but they're zips, not md5's or whatever. I can just ignore that and load the zip?
No via odin you have to take a tar file...and to restock propperly, take a three parted firmware and partition ticked with 512 pit.
Here is a thread with different tools and especially the first row, with rescue and recovery kits is what you need and can take.
http://forum.xda-developers.com/showthread.php?t=1796807&highlight=adb+download
or take slappys rescue kit, link is indcluded in an other of m post:
http://forum.xda-developers.com/showpost.php?p=36168807&postcount=5
managed to get back to stock via odin and one of the samfirmware packages. many thanks to all! :laugh:

[i537] Safestrap'd 4.2.2 to Root'd 4.4.2 Guide

Here is everything you need for a flawless upgrade from a 4.2.2 to 4.4.2 on the i537 hardware.
Step 0: Download this zip file. It has everything that we will need (except Odin3. Don't want my link/thread/post pulled).
Step 1 - Update from to 4.3.
Download and unzip the Stock ML2 4.3 image. Reboot your phone into Download Mode (Hold Volume Down while booting up, then press Volume Up when prompted). Don’t worry about current root, SafeStrap, etc - as it’s all going away soon.
Step 2 - Match up the file names to the four ‘Files’ sections in the lower right corner of Odin3. The individual filenames of the .tar.md5 files will be used as an identifier. Check “update bootloader” and click ‘Start’. Once it finishes and reboots into 4.3, enable USB debugging mode on the phone.
Step 2- Reboot into Download Mode. Apply Pwnedkernel 4.3 with Odin using the PDA File section.
Step3 - Now let the phone boot up. You will need USB Debugging enabled again, and ensure that you have USB ADB access.
Step 4 - Once ready, run Saferoot to the running pwned 4.3 image (install.bat for Windows, install.sh for Linux/Mac OS). Follow the terminal instructions until completion.
Reboot. Launch SuperSU and update the binary. Disable Knox with your new root access. Ignore any issues with Modems, etc.
Step 5 - Flash original 4.3 kernel back with Odin3 using the PDA File section.
Step 6 - Place your SafeStrap apk, PwnedKitKat, and SuperSU to your SD Card.
Step 7 - Install SafeStrap (make sure to launch it for the bootloader to install correctly)
Step 8 - Reboot into SafeStrap recovery. Flash PwnedKitKat.zip, followed by SuperSU.zip. Do not reboot in between, clear cache, or any other nonsense.
Step 9 - When finished, reboot back into DOWNLOAD MODE. Now flash the stock KitKat kernel using Odin3 (using the PDA File section).
Finished!
Shout-out to: Hashcode, My-blue-snog-box, TransformixS4, & Sunderwear. Y’all have kept me sane dealing with this phone and it’s locked bootloader.
casadelbeard said:
Finished!
Shout-out to: Hashcode, My-blue-snog-box, TransformixS4, & Sunderwear. Y’all have kept me sane dealing with this phone and it’s locked bootloader.
Click to expand...
Click to collapse
Great guide!
I'm glad I helped and thanks for the shout out!
I hope I will help you in more things!
-TransformixS4
Do I have to do a factory reset? Or simply clear cache/dalvik?
casadelbeard said:
Step 1 - Update from to 4.3.
Click to expand...
Click to collapse
I hate to be a nit picker, but shouldn't this say "from 4.2 to 4.3"?
Thanks for a great post and the zip file! Makes it nice n easy for us. Can't wait to flash later!
?
Tell me how do you download your zip because after an hour of "downloading to my pc" I yet have to see any file in any of my download folders.
2nd of all I made the mega account, tried downloading through the account to my pc, then through the cloud, then through the sync & still am unable to physically see any download happening onto my pc hdd... Although I respect the owner, Kim Dotcom there is something wrong since you can't simply even download a file like it is normally available, (a standard) through your browser..
Please explain to me how do you get the 1.67gb file onto the pc because I tried everything I could think of and I am unable to & I am not a noob.
This is the first time i stumbled upon something weird like this..
when i update to Kitkat on safestrap it says "Checking MD5 File... Skipping MD5 Check: no MD5 File found." Should i be worried?
casadelbeard said:
Here is everything you need for a flawless upgrade from a 4.2.2 to 4.4.2 on the i537 hardware.
Step 0: Download this zip file. It has everything that we will need (except Odin3. Don't want my link/thread/post pulled).
Step 1 - Update from to 4.3.
Download and unzip the Stock ML2 4.3 image. Reboot your phone into Download Mode (Hold Volume Down while booting up, then press Volume Up when prompted). Don’t worry about current root, SafeStrap, etc - as it’s all going away soon.
Step 2 - Match up the file names to the four ‘Files’ sections in the lower right corner of Odin3. The individual filenames of the .tar.md5 files will be used as an identifier. Check “update bootloader” and click ‘Start’. Once it finishes and reboots into 4.3, enable USB debugging mode on the phone.
Step 2- Reboot into Download Mode. Apply Pwnedkernel 4.3 with Odin using the PDA File section.
Step3 - Now let the phone boot up. You will need USB Debugging enabled again, and ensure that you have USB ADB access.
Step 4 - Once ready, run Saferoot to the running pwned 4.3 image (install.bat for Windows, install.sh for Linux/Mac OS). Follow the terminal instructions until completion.
Reboot. Launch SuperSU and update the binary. Disable Knox with your new root access. Ignore any issues with Modems, etc.
Step 5 - Flash original 4.3 kernel back with Odin3 using the PDA File section.
Step 6 - Place your SafeStrap apk, PwnedKitKat, and SuperSU to your SD Card.
Step 7 - Install SafeStrap (make sure to launch it for the bootloader to install correctly)
Step 8 - Reboot into SafeStrap recovery. Flash PwnedKitKat.zip, followed by SuperSU.zip. Do not reboot in between, clear cache, or any other nonsense.
Step 9 - When finished, reboot back into DOWNLOAD MODE. Now flash the stock KitKat kernel using Odin3 (using the PDA File section).
Finished!
Shout-out to: Hashcode, My-blue-snog-box, TransformixS4, & Sunderwear. Y’all have kept me sane dealing with this phone and it’s locked bootloader.
Click to expand...
Click to collapse
I do not understand which 4 files to put where
Match up the file names to the four ‘Files’ ... How do you MATCH them up. I only see one file to match up called CSC
What does the AP CL and CP and how do those match up to Bootloader PDA and PHONE ??
Display issues
As soon as I installed 442 kernel display issues popped up. The screen is brighter on the left than on the right with vertical lines running throughout.
Started whole process again... issues go away until 442 kernel is reapplied.
Any suggestions?
I was able to get Eclipse TW 4.02 SS ROM to boot and it looks very nice so far.. as close to AOSP as we will get. I started with the usual 4.3 > TR> SS 3.71 > NC9 Update >KK Kernel > SS3.73 upgrade path, then downloaded the newest eclipse 4.02 SS ROM and 4.4.2 i537 modules. I went ahead and inserted the modules into the eclipse ROM just to save an additional flash step, then flashed the new rom, wiped data,dalvik and cache then rebooted to download and flashed the KK i537 kernel on top. After a few minutes I'm at the setup screen.
So far the only issue I'm battling is the default camera FC, the Google camera app doesn't seem to work either
downloading issues?
baldusiek said:
Tell me how do you download your zip because after an hour of "downloading to my pc" I yet have to see any file in any of my download folders.
2nd of all I made the mega account, tried downloading through the account to my pc, then through the cloud, then through the sync & still am unable to physically see any download happening onto my pc hdd... Although I respect the owner, Kim Dotcom there is something wrong since you can't simply even download a file like it is normally available, (a standard) through your browser..
Please explain to me how do you get the 1.67gb file onto the pc because I tried everything I could think of and I am unable to & I am not a noob.
This is the first time i stumbled upon something weird like this..
Click to expand...
Click to collapse
I have downloaded the file 3 times now (accidentally deleted it the first, then ineeded it on a laptop at a friends house. Downloaded flawlessly. Im FAARRR from a noob, but honestly, a 10 year old could do it. I did my sons active and mine. Try using a differrnt browser or something. Only took about 20 minutes total to download the whole file. I used IE every time. I dont know if thays the dame browser you used but if not, then try that. (I know this post is a little older, but for someone like me who just picked up a couple actives this week it came in mighty handy. Thanks for the tutorial. Does anyone know of any 4.4.2 touchwiz based rome that I can use now that I have safestrap (3.73) running? Or is this basically all we are going to get. Im ok with that but woild love a deodexed TW rom to use. Have trued deodexing mine several times now and while it says thay it worked and is complete, its still odexed after reboot from recovery??!?!

install update on root-ed phone // is there a way

hello everybody
i've rooted my moto E4 plus, using this guide:
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-plus-guide-to-rooting-mediatek-t3668753
and everything worked well.. however - i would like to update my phone software, and i do not know what spell to cast now..
what is the best way to go now?
thanks
Restore stock firmware, that includes stock recovery.
ATTACK said:
Restore stock firmware, that includes stock recovery.
Click to expand...
Click to collapse
hi ATTACK, thanks for reply.
i've tried to restore scattered file (bunch of bin-s) using miracle box, but without success. it seams that miracle is not able to restore these files as phones firmware - or i am doing something wrong.
procedure:
i run miracle box, i choose adequate mtk version, i pick write mode, and select .txt (scatter file). in the same dir there are many .bin files..
what should i do?
thanks
vladimirnikolic said:
hi ATTACK, thanks for reply.
i've tried to restore scattered file (bunch of bin-s) using miracle box, but without success. it seams that miracle is not able to restore these files as phones firmware - or i am doing something wrong.
procedure:
i run miracle box, i choose adequate mtk version, i pick write mode, and select .txt (scatter file). in the same dir there are many .bin files..
what should i do?
thanks
Click to expand...
Click to collapse
i get messages:
Waiting for USB Port...
Set MediaTek PreLoader USB VCOM Port (COM7)
Please Hold "ON" to connect with the phone...
Connected to Phone.
CPU: MT6735 SW:0000 Ver: CB00
Downloading Boot8 ...
EMMC Size: 0x03A3E00000
Flash Type: EMMC
INT/EXT RAM Size: 0x0+0x0
Writing(Nand/eMMC)...
>>Error1: no 5A
.. update - i've tried with sp flash tool as well - but it seems that it cannot recognize the scattered file format. the software crashes when i try to load .txt file
Use fastboot to flash the .IMG files. There should be a guide somewhere. It's either here or in the Moto E4 fourm.
sp tools works fine form me.

REQ: Unshrink data partition

Hello!
Not sure if this has happened, but I think my data partition has shrunk. My device (s10e) used to show 107 GB, now it shows ~ 15.7 GB. Is there a way to un-shrink data partition and restore it? I have TWRP at the moment. Was about to install LOS17.1 but stopped.
Reason: I did the stupid thing even though you (topjohn)asked not to, "Never flash only an AP file, as Odin can shrink your /data file-system if you do." Someone in the forums had a thorough, detailed post, saying to flash tarred files to AP slot (did not mention by themselves or with other files as well).
Thanks!
goodflood said:
Hello!
Not sure if this has happened, but I think my data partition has shrunk. My device (s10e) used to show 107 GB, now it shows ~ 15.7 GB. Is there a way to un-shrink data partition and restore it? I have TWRP at the moment. Was about to install LOS17.1 but stopped.
Reason: I did the stupid thing even though you (topjohn)asked not to, "Never flash only an AP file, as Odin can shrink your /data file-system if you do." Someone in the forums had a thorough, detailed post, saying to flash tarred files to AP slot (did not mention by themselves or with other files as well).
Thanks!
Click to expand...
Click to collapse
Flashing Stock rom should fix it...
Sent from my moto g(7) play using Tapatalk
@PoochyX That did it; thank you so much!
I have a Samsung SM-T290, running Android 9. Whatever I do, Magisk seems to shrink my data partition from 32G to 8G. I think I scrupulously followed topjohnwu's directions (except that I put the stock AR module on the SD card and moved it between the device and my laptop via sneakernet rather than adb pull). I used Odin to flash BL, the patched AP, CP and CSC (not Home-CSC). Magisk was installed alright, and I achieved root, but my storage was reduced to 8GB.
The only way I've found so far to bring my storage up to 32GB was to factory reset, which removes Magisk and root. I tried extracting the PIT file from CSC in the stock ROM and doing a NAND erase and reformat, but as long as I'm using the patched AR with Magisk, I end up with 8GB.
What am I doing wrong?
Further to the above: Just to dot all the i's and cross all the t's, I repeated the process, using adb pull to transfer the patched AP file, as topjohnwu recommended. The same thing happened: my data partition was reduced to 8GB.
Also, I've noticed, that whenever I insert the patched AP into Odin, it accepts it almost immediately, while it takes quite a while reading the original AP tar. Could this indicate that Magisk is corrupting the AP tar file when it patches it?
pgurwitz said:
Further to the above: Just to dot all the i's and cross all the t's, I repeated the process, using adb pull to transfer the patched AP file, as topjohnwu recommended. The same thing happened: my data partition was reduced to 8GB.
Also, I've noticed, that whenever I insert the patched AP into Odin, it accepts it almost immediately, while it takes quite a while reading the original AP tar. Could this indicate that Magisk is corrupting the AP tar file when it patches it?
Click to expand...
Click to collapse
I think the speed difference is due to whether it's ending with n.n.tar.md5 or just n.n.tar. The time probably has to do with the unpacking of md5.
By the way: My capacity also shrunk from 32 to 16 GB on my Xcover 4s

Categories

Resources