This has been fixed. See chainfire post.
http://forum.xda-developers.com/showthread.php?t=1494114
I've taken a dump of a known CLEAN sbl1 and have tried restored it to a flashed i747. This did not work for me. If someone is willing to proof my process for accuracy, that would be nice.
Create the Backup from the good i747
Code:
dd if=/dev/block/mmcblk0p2 of=/mnt/extSdCard/backup/good/mmcblk0p2_sbl1.img bs=4096
Backup the existing BAD w/ the same command
Restore the good
Code:
boot into cwm
# replace /path/to/ w/ the actual path of the file.
#dd if=/path/to/mmcblk0p2_sbl1.img of=/dev/block/mmcblk0p2
Still stuck w/ same number of flashes.
I've additionally backed up all the partitions for both the bad and the good via the below:
Code:
#remove the echo to perform the backup you'll also want to change the target
echo dd if=/dev/block/mmcblk0p5 of=/mnt/extSdCard/backup/good/mmcblk0p5_aboot.img bs=4096
echo dd if=/dev/block/mmcblk0p20 of=/mnt/extSdCard/backup/good/mmcblk0p20_backup.img bs=4096
echo dd if=/dev/block/mmcblk0p7 of=/mnt/extSdCard/backup/good/mmcblk0p7_boot.img bs=4096
echo dd if=/dev/block/mmcblk0p17 of=/mnt/extSdCard/backup/good/mmcblk0p17_cache.img bs=4096
echo dd if=/dev/block/mmcblk0p11 of=/mnt/extSdCard/backup/good/mmcblk0p11_efs.img bs=4096
echo dd if=/dev/block/mmcblk0p19 of=/mnt/extSdCard/backup/good/mmcblk0p19_fota.img bs=4096
echo dd if=/dev/block/mmcblk0p21 of=/mnt/extSdCard/backup/good/mmcblk0p21_fsg.img bs=4096
echo dd if=/dev/block/mmcblk0p23 of=/mnt/extSdCard/backup/good/mmcblk0p23_grow.img bs=4096
echo dd if=/dev/block/mmcblk0p1 of=/mnt/extSdCard/backup/good/mmcblk0p1_modem.img bs=4096
echo dd if=/dev/block/mmcblk0p12 of=/mnt/extSdCard/backup/good/mmcblk0p12_modemst1.img bs=4096
echo dd if=/dev/block/mmcblk0p13 of=/mnt/extSdCard/backup/good/mmcblk0p13_modemst2.img bs=4096
echo dd if=/dev/block/mmcblk0p9 of=/mnt/extSdCard/backup/good/mmcblk0p9_pad.img bs=4096
echo dd if=/dev/block/mmcblk0p10 of=/mnt/extSdCard/backup/good/mmcblk0p10_param.img bs=4096
echo dd if=/dev/block/mmcblk0p16 of=/mnt/extSdCard/backup/good/mmcblk0p16_persist.img bs=4096
echo dd if=/dev/block/mmcblk0p18 of=/mnt/extSdCard/backup/good/mmcblk0p18_recovery.img bs=4096
echo dd if=/dev/block/mmcblk0p6 of=/mnt/extSdCard/backup/good/mmcblk0p6_rpm.img bs=4096
echo dd if=/dev/block/mmcblk0p2 of=/mnt/extSdCard/backup/good/mmcblk0p2_sbl1.img bs=4096
echo dd if=/dev/block/mmcblk0p3 of=/mnt/extSdCard/backup/good/mmcblk0p3_sbl2.img bs=4096
echo dd if=/dev/block/mmcblk0p4 of=/mnt/extSdCard/backup/good/mmcblk0p4_sbl3.img bs=4096
echo dd if=/dev/block/mmcblk0p22 of=/mnt/extSdCard/backup/good/mmcblk0p22_ssd.img bs=4096
echo dd if=/dev/block/mmcblk0p14 of=/mnt/extSdCard/backup/good/mmcblk0p14_system.img bs=4096
echo dd if=/dev/block/mmcblk0p8 of=/mnt/extSdCard/backup/good/mmcblk0p8_tz.img bs=4096
echo dd if=/dev/block/mmcblk0p15 of=/mnt/extSdCard/backup/good/mmcblk0p15_userdata.img bs=4096
Advise welcome.
Please post steps you've taken to try and reset the counters.
+1 I rooted via SGS3 ToolKit program and executed a few times to get rooted and CWM installed, now my counter is up at 6.
There must be a way this gets reset and this is why I say this:
I followed the no trip method to install rooted stock and used the adb shell dd commands to write the cwm recovery. All was well, I had no flash counter and device status showed normal. I flashed other roms using cwm and even flashed cwm using cwm a few times. I used the dd commands to write a different cwm image in adb shell and noticed that device status showed modified. Now, I had never ever ever flashed anything with odin except the stock rom and the stock rooted rom per the no trip instructions. I was perplexed, but figured I just didn't know enough about what I was doing and screwed something up...oh well. Tonight, I flashed the stock rooted rom using odin, again no trip instructions. The dd'd the latest touch cwm 5.8.4.7. Flashed a few things in cwm, most notably update package that didn't disable search funtionality. I noticed device status says normal again, and the bootloader screen doesn't show a counter nor does anything point to custom.
I don't know if any of that means anything to anyone working on this, but thought I would share.
Device Status != Flash Counter
lordmorphous said:
There must be a way this gets reset and this is why I say this:
I followed the no trip method to install rooted stock and used the adb shell dd commands to write the cwm recovery. All was well, I had no flash counter and device status showed normal. I flashed other roms using cwm and even flashed cwm using cwm a few times. I used the dd commands to write a different cwm image in adb shell and noticed that device status showed modified. Now, I had never ever ever flashed anything with odin except the stock rom and the stock rooted rom per the no trip instructions. I was perplexed, but figured I just didn't know enough about what I was doing and screwed something up...oh well. Tonight, I flashed the stock rooted rom using odin, again no trip instructions. The dd'd the latest touch cwm 5.8.4.7. Flashed a few things in cwm, most notably update package that didn't disable search funtionality. I noticed device status says normal again, and the bootloader screen doesn't show a counter nor does anything point to custom.
I don't know if any of that means anything to anyone working on this, but thought I would share.
Click to expand...
Click to collapse
The device status in About Device is different from the flash counter in the Download screen.
There is a background job that looks at important files in /system and changes the device status to modified when it finds them. For example, installing busybox will change that to modified ... eventually. It may not show up as soon as you boot, but if you wait long enough it will. This is no big deal, really, because if you were to return your device, you'd flash back to stock first and the device status would go back to Normal.
The flash counter, on the other hand, records when you flash an unsigned recovery or kernel through Odin. (It may be tripped by other Odin flashes, but we know flashing an unsigned system image doesn't, which is how we can get root without tripping the counter.) Once this counter is incremented, we don't (yet) know how to reset it. This may be a big deal because your provider could check this counter if you had to return your device and deny warranty coverage.
c0ns0le said:
I've taken a dump of a known CLEAN sbl1 and have tried restored it to a flashed i747. This did not work for me. If someone is willing to proof my process for accuracy, that would be nice.
Click to expand...
Click to collapse
Can you post the clean sbl1?
What was done on the Note
The developer Braway on the Galaxy Note took a diffenet approach. He had a process keep incrementing the counter until it cycled around and hit 0 again. Not sure of the exact steps but it took about 10 seconds to run it's magic and you where then back at 0.
SkipKelley said:
The developer Braway on the Galaxy Note took a diffenet approach. He had a process keep incrementing the counter until it cycled around and hit 0 again. Not sure of the exact steps but it took about 10 seconds to run it's magic and you where then back at 0.
Click to expand...
Click to collapse
Interesting
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
SkipKelley said:
The developer Braway on the Galaxy Note took a diffenet approach. He had a process keep incrementing the counter until it cycled around and hit 0 again. Not sure of the exact steps but it took about 10 seconds to run it's magic and you where then back at 0.
Click to expand...
Click to collapse
Interesting.. I wonder how that affects the nand chip and if the memory allocation for the counter is the same on the gs3 as it is on the note. Would totally suck balls if it was a dword, requiring 4294967295 flashes before it rolls over..
SkipKelley said:
The developer Braway on the Galaxy Note took a diffenet approach. He had a process keep incrementing the counter until it cycled around and hit 0 again. Not sure of the exact steps but it took about 10 seconds to run it's magic and you where then back at 0.
Click to expand...
Click to collapse
With that method, braway said that Samsung could still tell something was flashed, and what the last thing flashed was. Doesn't this mean that our warranty would still be void?
braway said:
Fun Fact
- Samsung knows how many kernels/recoveries you've flashed through odin.
- The single counters are up to 255, so theoretically you can "reset" by flashing 256 of each (Samsung will still know you flashed something)
- Samsung knows what was the last thing you've flashed
- Flashing System is not counted.
Click to expand...
Click to collapse
drothenberger said:
The device status in About Device is different from the flash counter in the Download screen.
There is a background job that looks at important files in /system and changes the device status to modified when it finds them. For example, installing busybox will change that to modified ... eventually. It may not show up as soon as you boot, but if you wait long enough it will. This is no big deal, really, because if you were to return your device, you'd flash back to stock first and the device status would go back to Normal.
The flash counter, on the other hand, records when you flash an unsigned recovery or kernel through Odin. (It may be tripped by other Odin flashes, but we know flashing an unsigned system image doesn't, which is how we can get root without tripping the counter.) Once this counter is incremented, we don't (yet) know how to reset it. This may be a big deal because your provider could check this counter if you had to return your device and deny warranty coverage.
Click to expand...
Click to collapse
I have flashed Nostagia and some of the cm nightlies with cwm and no tripping of the flash counter yet. Is there anything that flashing with cwm will trip the counter? Is there any reference that says what will or will not trip the flash counter? If not, oh well; it just makes things more exciting I guess. I do miss the old days of captivate. I threw everything at my captivate. When I exchanged it for a new phone (was within a month), I just odin flashed to stock. No one was any the wiser :angel:
Nothing in cmw will ever trip the flash clunter
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
file name is inconsequential. dd simply takes whatever comments of the 'if=' and does a block for block copy to 'of='.
Anyone know what is actually in the sbl1? I'm to lazy to go look right now.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
c0ns0le said:
file name is inconsequential. dd simply takes whatever comments of the 'if=' and does a block for block copy to 'of='.
Anyone know what is actually in the sbl1? I'm to lazy to go look right now.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
This thread has some interesting information: http://forum.xda-developers.com/showthread.php?t=1769411. It's from the Verizon phone, but I'll bet it's the same for all of them. Adam doesn't know what it is, but he's pretty sure it's signed by Samsung. My mostly uneducated guess is that if it's signed, it's not where the flash counter is stored (since changing a bit in sbl1 might break the signature). We could easily verify that by comparing the sbl1 from a phone with a tripped counter with one without. We'd also have to compare the sbl1 from two phones without the tripped counter to see if they are identical on every phone.
The AT&T UCALG1 OTA update flashed sbl2 (mmcblk0p3), sbl3 (0p4), aboot (0p5), rpmfw (0p6), and tz (0p8) so I'm guessing those don't contain the counter, either.
Would seem to make sense.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Is this where it ends? Please don't let it stop without a fix.
Sent from my SAMSUNG-SGH-I747 using xda premium
Not sure if this helps. I'm not able to try it out yet, but if anyone else is able to confirm it works on the AT&T variant I'm sure it would be appreciated by all
Ignore my old link to a manual way of resetting custom flash counter. Chainfire updated his Triangle Away up to save us: http://forum.xda-developers.com/showthread.php?t=1494114
It sounds like it works for AT&T (for sure I used it), plus all other variants.
johnhazelwood said:
Not sure if this helps. I'm not able to try it out yet, but if anyone else is able to confirm it works on the AT&T variant I'm sure it would be appreciated by all
http://forum.xda-developers.com/showthread.php?t=1781471
Click to expand...
Click to collapse
It worked on my AT&T!! Custom Binary Download: No - Current Binary: Samsung Offical - System Status::laugh: still says Custom. Will flash Odin stock to see if that will change. I will report back.
wbounds said:
It worked on my AT&T!! Custom Binary Download: No - Current Binary: Samsung Offical - System Status::laugh: still says Custom. Will flash Odin stock to see if that will change. I will report back.
Click to expand...
Click to collapse
Flashing stock should resolve the custom flag. I know it did for me.
johnhazelwood said:
Flashing stock should resolve the custom flag. I know it did for me.
Click to expand...
Click to collapse
It worked!!:fingers-crossed:
How does this compare to someone who has not tripped their counter?
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
If this is correct then we got it and returns are possible
The updated Triangle Away on the market works on my AT&T S3. It went from 3 to 0.
Related
Hi I plan to unroot my phone for warranty purposes.
I'm using a Desire Z with
baseband: 12.28b.60.140eU_26.03.02.26_M
build: 1.34.707.5 CL273326 release-keys
I've rooted the phone using gfree method.
This is what I plan to do:
1) Restore back to stock ROM (done)
2) Restore stock recovery.
- i have extracted the recovery.img from this RUU:
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M_release_155556_signed.exe
- Will be flashing using this guide:
http://forum.xda-developers.com/showthread.php?t=902493&highlight=flash_image
-Yet to flash that .img
3) S-on.
- Using this guide:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Turning_S-On
4) Restore factory settings.
I have extracted the .img from the RUU i mentioned. My question is whether that .img is flashable on all Desire Zs because it is the same RUU that was featured in the rooting procedure for build 1.72.
I understand that there has been a lot of unrooting threads, but none seem to deal specifically with the compatibility of the recovery image.
Any help is much appreciated.
I'm not sure that if I just skip to S-on then the custom recovery (CWM in this case) will not show up. Does it?
Can anyone help?
I just need to know whether recovery images from different Vision RUUs (except TMOUS ones) are identical and flashable on any Desire Z.
As mentioned I already have a stock recovery.img from a 1.34 RUU, but the location ID might not be the same. Are stock recovery images dependent on location IDs?
The recovery should be completely independent from the CID. If the partitioning scheme is the same (and you can check that by verifying if the sizes of the images that make up your original ROM and those of the RUU are identical) you should be fine.
Cool. I went ahead with flashing the stock recovery and sure enough my phone isn't bricked and when I boot into recovery, it is of a red triangle.
Weirdly enough ROM Manager still tells me I have CWM 2.5.1.3 though...
Guess ppl can start using that recovery.img as a stock recovery.
Thanks a thousand times!
EDIT:
I tried to S-On using the guide on the Wiki but it did not work.
So i tried using terminal emulator to do the following:
# cd /data/local
# chmod 777 gfree
# ./gfree -s on
Click to expand...
Click to collapse
sure enough when i booted into (trackpad + power button) i see it say s-on.
Am i officially 'unrooted' now?
There was supposed to be a 'sync' command after './gfree -s on', but I forgot to do it. Am I still good to go?
You're okay. The sync command makes sure the caches are written to disk, but since you are S-ON it means they were written.
so if it so happened this phone gets returned to me after warranty claims, so I just
# cd /data/local
# chmod 777 gfree
# ./gfree -s off
to turn it s-off again? Or do I need to go through running rage again?
UPDATE: Got my phone back. Had to re-root the phone all the way from running rage.
weirdly enough, although the bootloader screen shows S-on, I am still able to use shootme? This means I'm still rooted, am I right?
Yup. Remove the Superuser app and it at least shouldn't be as obvious that you're rooted
hrmm superuser doesn't seem to be removable by conventional means... I don't remember installing it either. When I push it to the phone, I pushed it to the sdcard. Now i booted the phone without the sdcard, but superuser is still there...
Do I restore factory settings instead?
EDIT: nvm, Factory reset-ed. Everything looked factory. Wish me luck.
Nice, glad everything worked out...
djfoo000, glad it all worked out for you.
I have a Bell Desire Z, like yours and wanted to do something similar. While your steps are clear, i just wanted to confirm a few points:
1. In your very first post, when you said "Restore back to stock ROM (done)" i am guessing (99% sure) you meant that you restored back the ROM which you had backed up right after you installed ClockworkMod? Or did you use some other ROM image?
2. So even after you used gfree to turn back S-ON, you still had root privileges because of Superuser. How about after you did the factory reset, which presumably removed Superuser - did you still have root privileges?
3. Would it be possible for you to upload the stock recovery img file somewhere? If not, its okay as well.
Thanks
1) Yes. That stock ROM i mentioned was of a nandroid backup that restored everything prior to flashing a ROM that restored everything including apps and an unfinished Angry Birds (haha), instead of a clean one.
2) Yeah weirdly enough ShootMe still snaps screenshots. My guess is that root access is needed to install shootme as a system app and is not required beyond that. So even after s-on, shootme continues to operate due to it already being in the system app folder.
After I factory reset-ed, superuser and terminal emulator was gone. Since I was in a hurry to return the phone to the dealer I did not bother to download terminal emulator to input the 'su' command to check for root privileges. Sorry if it did not answer your question regarding root after factory reset.
3) Here's the file I extracted:
http://www.megaupload.com/?d=K8DVSNLX
I'm not 100% sure if it'll work on other Desire Zs since mine was not a carrier branded Desire Z.
Best of luck!
Excellent. Thanks djfoo000.
Couple of more questions -
1. do you know of any way for me to backup my existing recovery? I still havent installed CwM or other recovery image on my Desire Z (still stock).
Fastboot has commands to erase the recovery or flash a new one, but nothing that i could find to backup current recovery.
2. Also, would having S-ON and CID as 111111111 have any impact on doing a factory reset through stock recovery on the stock ROM? I dont think it will turn S-OFF and even more unlikely that it will change the CID, but will it do anything else? like go into a boot loop or some other weird thing?
lol i'm a noob user just like you. I just happen to gather enough info to do what I wanted to do.
1) I have no idea of a way to backup the stock recovery. Maybe searching the phone for a recovery.img (if there ever is one in the phone) and pull that?
2) I dunno anything about CIDs...
Might need help from other senior users from the forums.
testerman123 said:
1. do you know of any way for me to backup my existing recovery? I still havent installed CwM or other recovery image on my Desire Z (still stock).
Fastboot has commands to erase the recovery or flash a new one, but nothing that i could find to backup current recovery.
2. Also, would having S-ON and CID as 111111111 have any impact on doing a factory reset through stock recovery on the stock ROM? I dont think it will turn S-OFF and even more unlikely that it will change the CID, but will it do anything else? like go into a boot loop or some other weird thing?
Click to expand...
Click to collapse
1. There may well be a stock ROM/RUU image that you can pull that stock recovery from, as you've mentioned above. Or if not, you could always "dd" the recovery partition to back it up, though I double that will be necessary.
2. Did you mean S-OFF ? No, it won't have any impact, the factory reset won't touch the radio config partition, which is where S-OFF, SuperCID etc are stored.
Thanks djfoo000 for trying - you have been helpful.
Steviewevie, thanks for responding.
I think dd would be the answer as well, now the only question is where is the recovery located? like the "if=" parameter.
After that off to the races with CwM (and a nandroid backup of my existing firmware, of course), and a custom ROM! Steviewevie and djfoo000 - didnt notice a mention of any custom roms you guys were using. any suggestions?
Edit:
Looked around a little bit to see what the if parameter would be.
when i did
$ su
# cat /proc/mtd
under adb shell and terminal emulator, i did not get a list of partitions.
BUMP!! anyone?
testerman123 said:
Looked around a little bit to see what the if parameter would be.
when i did
$ su
# cat /proc/mtd
under adb shell and terminal emulator, i did not get a list of partitions.
Click to expand...
Click to collapse
The G2 does not use raw flash, so partitions will not show up as mtd devices. You should be able to do a
# cat /proc/emmc
if you are just trying to see the partition map...
Thanks ianmcquinn! That worked great.
Got my hboot, recovery and boot backed up just in case.
The curious thing, though, is that the stock unbranded recovery from 1.34.405.5 RUU that djfoo uploaded is only 3.85MB, while my backed up recovery is 8.5MB. whats up with that?
i can confirm that when I flash the recovery.img i uploaded, the unrooting works fine. And it is 3.85MB as mentioned.
Hi
i have V20c Stock ROM and its rooted ( lg p930)
i didnot know v20c boot loader is locked and install clockworkmod 6.0.1.5 via rom manager
now it donot go to stock recovery mod for factory reset.
i need to factory reset my phone and it has many problems and errors , how can i unistall and remove cmw ?
every time i try to do a factory reset phone dont boot and try to go cwm recovery menu
here is the screenshot
HELP PLEASE !!
Do you have a backup of the recovery partition? If so, you can flash it back if you have root.
If not, you can follow this guide in full and you will be returned to a rooted V20c: http://forum.xda-developers.com/showthread.php?t=1969070
If however you want CWM, you will need to follow the unbricking guide.
drumist said:
Do you have a backup of the recovery partition? If so, you can flash it back if you have root.
If not, you can follow this guide in full and you will be returned to a rooted V20c: http://forum.xda-developers.com/showthread.php?t=1969070
If however you want CWM, you will need to follow the unbricking guide.
Click to expand...
Click to collapse
Thanx for your help
This is my first android phone , i just wana have the stock recovery menu, is there any other ways ?
What is back up of recovery partition and how to make it ?
My phone is working now and i did root it from this way : http://forum.xda-developers.com/showthread.php?t=1886460
if i should change the rom and update it again how much is the risk of doing this process?
Sent from my LG-P930
nss007 said:
Thanx for your help
This is my first android phone , i just wana have the stock recovery menu, is there any other ways ?
What is back up of recovery partition and how to make it ?
My phone is working now and i did root it from this way : http://forum.xda-developers.com/showthread.php?t=1886460
if i should change the rom and update it again how much is the risk of doing this process?
Sent from my LG-P930
Click to expand...
Click to collapse
Well that's certainly interesting. Sure enough the method you linked to does work with the AT&T V20c ROM. I don't think anyone here was aware of this method.
In that case, you can restore the recovery using the file I attached to this post (see below). Extract it and place the img file on your phone's SD card. Then use terminal emulator (from the market) or adb to issue the following commands:
Code:
su
dd if=/sdcard/v20c-recovery.img of=/dev/block/mmcblk0p13
Then you should be back to normal. Be extra careful when typing the last part of that (mmcblk0p13) as typing the wrong number on the end can potentially brick the phone.
Thanx i'll try the file you attached
Yes i used this method and i confirm that it can root the v20c very easy but do not unlock the bootloader
Sent from my LG-P930
drumist said:
In that case, you can restore the recovery using the file I attached to this post (see below). Extract it and place the img file on your phone's SD card. Then use terminal emulator (from the market) or adb to issue the following commands:
Code:
su
dd if=/sdcard/v20c-recovery.img of=/dev/block/mmcblk0p13
Then you should be back to normal. Be extra careful when typing the last part of that (mmcblk0p13) as typing the wrong number on the end can potentially brick the phone.
Click to expand...
Click to collapse
thanx, it works
i have another question !
what are the benefits of cyanogen rom into ics stock rom ?
does it worth i flash cyanogen or other custom roms ?
For those who are stuck in the "Brickloop" after restoring a backup in TWRP. See "Edit 2"...
____________________________
Edit : This seems to be the fix.. Worked for me and others who have tried .. :thumbup:
1. Install Stock firmware via Odin, then re-run auto-root (to regain root of course)
2. Install TWRP 2.6.3.2 via odin, reboot to recovery.
3. Do an "adb shell" when phone is in recovery mode to run commands via TWRP.
From the ADB shell: Wiped the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
(the last two commands probably did nothing, but thats what I did anyway)
Do a factory reset, reboot system
Afterwards, no more boot looping, the phone successfully registered on the mobile network, and my IMEI is there and correct. Seems like the EFS partition can rebuild itself now I guess...
Gotta love the XDA community !!!:highfive:
Edit 2
You can also try just running Commands via TWRP before using Odin to revert to stock, re-rooting etc..Worked for me while I was doing some restore testing with Jovy's modded kernel ..Just trying to save you some time..
Using TWRP Terminal Command To Complete this evolution...
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command"
3. Hit "Select" (lower right corner)..Do not select any specific folder, just hit select..
4. keyboard will open, type in the following commands, make sure you put the spaces and / where they need to be, it needs to look exactly as outlined..
mke2fs /dev/block/mmcblk0p12
Hit Go - The command will run.
Clear the box, type the following command
mkdir /efs
Hit Go - The command will run.
Clear the box, type the following command
mount -t ext4 /dev/block/mmcblk0p12 /efs
Hit Go - The command will run.
You can now back out of the terminal command, and follow the rest of the directions.
Also, if you plan on flashing custom ROM's after getting out of the loop, use TWRP ver 2.6.3.1.
Updated : Please see updated TWRP thread for latest information regarding release Version. 2.3.6.8
Steve Lazarus said:
Just trying to provide a thread for those of us "Early Adopters" that have encountered the boot loop issue trying to restore in TWRP 2.6.3.1
If anyone has any crazy ideas they would like me to try to resolve this issue, please let me know. I encountered the Boot Loop this morning trying to restore a backup, nothing will fix it, Odin, Re-Flash etc... NOTHING to this point will resolve the issue. I have been in contact and walked through various attempts by some great folks (Dev's here) with no luck as yet...
Early adopters please be advised to download the newest release 2.6.3.2, I can not vouch for that release as my phone is currently in a soft brick state
Let's get this figured out !!! My guess is we need a stock PIT file, anyone have one laying around ??
Click to expand...
Click to collapse
you try this to help you http://www.youtube.com/watch?v=0U3x9f_0qLM&list=FLzlWiSvUo6qQhHdETAHc7vQ&index=1
how did yours get soft bricked again sorry?
chrisa887 said:
you try this to help you http://www.youtube.com/watch?v=0U3x9f_0qLM&list=FLzlWiSvUo6qQhHdETAHc7vQ&index=1
how did yours get soft bricked again sorry?
Click to expand...
Click to collapse
Trying to "Restore" a backup this morning....
Got another one coming, so I have this one to experiment on for fixes for a couple day's. Hopefully we can get it figured out... Seems to be a partition issue (my guess anyway), need to get a stock PIT file to flash in Odin, at least we can see if that's it..? Rule it out, or determine it's the culprit.
That's such a bummer. Keeping an eye on this thread and will report anything i find. 4th one I've seen..
Have there been any reports of this on ATT or other versions?
Sent from my SM-N900T using Tapatalk 4
Steve Lazarus said:
Trying to "Restore" a backup this morning....
Got another one coming, so I have this one to experiment on for fixes for a couple day's. Hopefully we can get it figured out... Seems to be a partition issue (my guess anyway), need to get a stock PIT file to flash in Odin, at least we can see if that's it..? Rule it out, or determine it's the culprit.
Click to expand...
Click to collapse
can you get it into download mode
Steve Lazarus said:
Just trying to provide a thread for those of us "Early Adopters" that have encountered the boot loop issue trying to restore in TWRP 2.6.3.1 as to avoid cluttering up that thread with our issue.
If anyone has any crazy ideas they would like me to try to resolve this issue, please let me know. I encountered the Boot Loop this morning trying to restore a backup, nothing will fix it, Odin, Re-Flash etc... NOTHING to this point will resolve the issue. I have been in contact and walked through various attempts by some great folks (Dev's here) with no luck as yet...
Early adopters please be advised to download the newest release 2.6.3.2, I can not vouch for that release as my phone is currently in a soft brick state
Let's get this figured out !!! My guess is we need a stock PIT file, anyone have one laying around ??
Click to expand...
Click to collapse
When in TWRP did you go into settings and check Use rm -rf instead of formatting like AssassinsLament said to.......................................... >
chrisa887 said:
can you get it into download mode
Click to expand...
Click to collapse
Oh yeah, when I say we tried everything, WE TRIED EVERYTHING !!! Flashing stock via Odin, Relfashing TWRP through Odin and trying to install custom ROM, various portions of all of the above etc.... Think the partition needs fixed, only way to do that is with a PIT file to flash via Odin.. Does anyone know how to extract or create the stock PIT from the Note 3 ?
deeznutz1977 said:
When in TWRP did you go into settings and check Use rm -rf instead of formatting like AssassinsLament said to
Click to expand...
Click to collapse
Negative, I'll give that a try....
Steve Lazarus said:
Oh yeah, when I say we tried everything, WE TRIED EVERYTHING !!! Flashing stock via Odin, Relfashing TWRP through Odin and trying to install custom ROM, various portions of all of the above etc.... Think the partition needs fixed, only way to do that is with a PIT file to flash via Odin.. Does anyone know how to extract or create the stock PIT from the Note 3 ?
Click to expand...
Click to collapse
There are some pit file tools out there.
I believe this is what you are looking for
Heimdall Suite
http://forum.xda-developers.com/showthread.php?t=1916936
les_garten said:
There are some pit file tools out there.
Click to expand...
Click to collapse
Yep, problem is I don't know what the stock PIT looks like, phone is currently locked into handicapped mode lol
deeznutz1977 said:
When in TWRP did you go into settings and check Use rm -rf instead of formatting like AssassinsLament said to.......................................... >
Click to expand...
Click to collapse
Made it worse, didn't even get to the T-Mob splash screen, got stuck on the initial Note 3 screen... Previous attempts made it to the T-Mob splash screen, on occasion it would actually just get into the launcher when I'd get "System Process Failed" with the option to wait or cancel. Regardless of selection, or just letting it sit there for a minute, would throw it back into a boot loop...
So for this attempt
Installed TWRP via Odin
Checked rm - rf
Wiped, Factory Reset
Tried installing Darthstalker / Deodexed Stock
No Luck..
Steve Lazarus said:
Yep, problem is I don't know what the stock PIT looks like, phone is currently locked into handicapped mode lol
Click to expand...
Click to collapse
I think you would need to get someone with a TMO N3 to make one for you.
les_garten said:
I think you would need to get someone with a TMO N3 to make one for you.
Click to expand...
Click to collapse
Exactly....:good:
Just hoping someone with the know how chimes in!!!! Would be sweet !!
Steve Lazarus said:
Exactly....:good:
Just hoping someone with the know how chimes in!!!! Would be sweet !!
Click to expand...
Click to collapse
I'd be interested in doing this but won't have mine till who knows when with Negri!
So I just tried another Odin reflash, out of curiosity, while I was watching the messages in Odin, it say's "Get PIT for mapping" does it always say that, or is it telling me that's the problem. Just that I've never reviewed everything that comes up in that window before...
Steve Lazarus said:
So I just tried another Odin reflash, out of curiosity, while I was watching the messages in Odin, it say's "Get PIT for mapping" does it always say that, or is it telling me that's the problem. Just that I've never reviewed everything that comes up in that window before...
Click to expand...
Click to collapse
Did it work
Sent from my SM-N900T using Tapatalk now Free
Hello,
Same problem here on N9005 after restore
Hayaa said:
Hello,
Same problem here on N9005 after restore
Click to expand...
Click to collapse
Hey and welcome to the family !!!
But seriously, bummer and hopefully we'll get it sorted eventually. I truly am sorry!!!
chrisa887 said:
Did it work
Sent from my SM-N900T using Tapatalk now Free
Click to expand...
Click to collapse
Nope, same sheet...
I'd appreciate any help I can get guys.
So today, for the first time ever I rooted my android.
Found a simple video on how to and it worked. I then wanted to try a custom rom [Cyanogenmod 12?] On a video it was said to have a custom recovery rom first. Well, I tried Flashing TWRP. It asked to reboot. I pressed "yes Please". After that it restarted and was stuck at:
"Could not do normal boot" Odin mode (High speed)
I did a reset and now its just at:
"Odin mode(high speed)"
I saw someone on a random forum describing the same problem. He said he fixed it installing a recovery rom. Im guess from odin
since I cant do things on my phone. But I don't even know how to go about it. I just now I need a Tar. file
Please give me direction .__.
Try TWRP tar from Odin with phone in download mode; TWRP recovery tar linked below.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
If that doesn't work, you may have to Odin the stock tar.
I'm wondering if you misread the CF Auto root prompt to update the su binary? Update the su binary but don't choose the TWRP option even if you have TWRP. If you get recovery working, delete the cache and dakvik cache and reboot.
Didn't work out...at least the way I did it. I'm still new to this. Id appreciate more broken down instructions if youre willing to help
Sixgotfangs said:
Didn't work out...at least the way I did it. I'm still new to this. Id appreciate more broken down instructions if youre willing to help
Click to expand...
Click to collapse
What version of Odin do you have? Should be 3.07 with C.F. auto root. What have you flashed in Odin? Not familiar with the Odin message you gave; did anything change with the new recovery tar flash in Odin?
Won't boot or flash recovery? If so, you need to factory reset and Odin stock tar.
https://www.androidfilehost.com/?fid=95853297432265112
The instructions for stock tar are below but it's important to remember when flashing stock tars to power down first prior to going to download. You may not have any choice but power down to reach download mode; pull battery if you can't power down.
http://forum.xda-developers.com/showthread.php?p=56853325
If you can't factory reset, Odin the stock tar and see if it boots.
Yes, I have the 3.07. Only thing ive done was Root. I tried the recovery rom from a mobile download. That's as far as I got. All the recovery files I get never end up showing in the pda file search. .tar or .md5 is what it calls for. If I CAN factory reset from where im at now how do I do so. If I can start ALL over with someone who is actually up to date and knows what theyre doing id feel more comfortable. right now nothings happened and my phone is still at "odin mode (hgh speed) --downloading.
Sixgotfangs said:
Yes, I have the 3.07. Only thing ive done was Root. I tried the recovery rom from a mobile download. That's as far as I got. All the recovery files I get never end up showing in the pda file search. .tar or .md5 is what it calls for. If I CAN factory reset from where im at now how do I do so. If I can start ALL over with someone who is actually up to date and knows what theyre doing id feel more comfortable. right now nothings happened and my phone is still at "odin mode (hgh speed) --downloading.
Click to expand...
Click to collapse
ok, check my post above for updates.
Also, don't use the phone to download tar files unless you're using Flashify from Google Play. Download the tars on PC, move to folder that Odin resides in to find easily. You'll need to open the archive and drag the files there if zipped. The stock tar should be zipped but not sure about the recovery tar.
Cant believe I didn't see the last section on that post. Sorry about that. Anyway, I am downloading those files. Looks like its gonna take some time though. I'll go through each step you said and let you know.
Forgot to mention that you should close Odin after each flash attempt. You may have already noticed by now.
To get to CM after stock tar:
1) Root with CF Auto root, update su binary/reboot (you should wait no longer than 5 minutes for Knox prompt from supersu.
2) Odin TWRP recovery tar using same method as stock tar; Odin will only write over stock recovery on this step.
3) factory reset and flash CM in recovery. But also follow suggested instructions in the ROM you choose.
So far so good. The lil blue loading bar is filling.
got back to rooting. but I didn't do anything else. haven't even went to super user
Sixgotfangs said:
got back to rooting. but I didn't do anything else. haven't even went to super user
Click to expand...
Click to collapse
Booted? That's good news!
Can't remember if you have to open it or not. You should get a superuser update and possibly a su binary update but not so important going to another ROM. The su binary update is the one that I was suggesting not to use the TWRP option; I think the option is normal? Eventually, you should get the pop-up to disable Knox notifications; reboot if takes longer than 5 minutes.
Ready for TWRP? Use Odin. Flashify is something you could look into for updating TWRP, as needed. It's good for backing up recoveries and kernels, too. But watch those kernels for installed lib modules; Flashify won't restore those properly. Rely on flash zips for those; same applies for stock kernels, zip should include the stock modules.
It's late; you're probably done for the night. I'm out too.
samep said:
Booted? That's good news!
Can't remember if you have to open it or not. You should get a superuser update and possibly a su binary update but not so important going to another ROM. The su binary update is the one that I was suggesting not to use the TWRP option; I think the option is normal? Eventually, you should get the pop-up to disable Knox notifications; reboot if takes longer than 5 minutes.
Ready for TWRP? Use Odin. Flashify is something you could look into for updating TWRP, as needed. It's good for backing up recoveries and kernels, too. But watch those kernels for installed lib modules; Flashify won't restore those properly. Rely on flash zips for those; same applies for stock kernels, zip should include the stock modules.
It's late; you're probably done for the night. I'm out too.
Click to expand...
Click to collapse
Yeah, things are back to normal. Thanks again. As for the next steps, pretty lost. Im going to check the play store for an superuser update but the SU binary update....that's where I start getting lost. sorry for not being up to date with the terminology. But I am gonna check back on those links and look for the TWRP. and then use it like I did for those last files...{that's what Im getting from your messages} correct me if im straying from the path lol. catch ya later
I'm confusing you a bit with the the su binary update and SuperSU update. To keep it simpler, that can wait until after you flash CM, if that's your goal. Those are prompts so don't be too concerned. Don't think you'll see Knox in CM.
So to keep it simple, you need TWRP to flash a custom ROM. I suggest the Odin tar in the link sent earlier.
After getting your custom ROM flashed in recovery, follow the prompts but if you see the su binary update prompt, don't choose the TWRP option. I think that caused your initial recovery issue but can't say for sure.
samep said:
I'm confusing you a bit with the the su binary update and SuperSU update. To keep it simpler, that can wait until after you flash CM, if that's your goal. Those are prompts so don't be too concerned. Don't think you'll see Knox in CM.
So to keep it simple, you need TWRP to flash a custom ROM. I suggest the Odin tar in the link sent earlier.
After getting your custom ROM flashed in recovery, follow the prompts but if you see the su binary update prompt, don't choose the TWRP option. I think that caused your initial recovery issue but can't say for sure.
Click to expand...
Click to collapse
Hey there, Ok so. After messing around I ended up getting that TWRP package to work. I thought It was a SINGLE file, that's where I got stuck. but the whole ?.rar showed up in the pda selection In odin and I ran it. Worked fine. didn't see anything about updates ...still.
I restarted and went to recoverymode. Teamwin popped up like ive seen from other videos. Guessing im on the right track. So right now I don't need to be worrying about SuperSu or Rashr? or should I be dealing with those two apps? ALSO is Rom installer anything to pay attention to?
At this point, you can look into a ROM installer or Flashify but I'd recommend just following the developer OP for whatever ROM you choose.
And yes, no need to worry with SuperSU or su binary update. Just follow the prompts when they appear after flashing ROM.
samep said:
At this point, you can look into a ROM installer or Flashify but I'd recommend just following the developer OP for whatever ROM you choose.
And yes, no need to worry with SuperSU or su binary update. Just follow the prompts when they appear after flashing ROM.
Click to expand...
Click to collapse
Thanks so much! The videos ive seen have been much simple-r for installing roms SO I may survive this whole experience after all...Yesterday was kind of a bad time to almost loose my phones functionality....being on the job hunt and all. need those phone calls Lol. So thanks again. Im hoping to try out cyanogenmod 12. I'll definitely shoot off a flare gun if I fail lol.
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
samep said:
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
Click to expand...
Click to collapse
SUCCESS! Thanks again Sensei Lol
samep said:
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
Click to expand...
Click to collapse
eh...celebrated too early I guess. Ever run into camera connection errors?
Sixgotfangs said:
eh...celebrated too early I guess. Ever run into camera connection errors?
Click to expand...
Click to collapse
Is the error while still on stock or CM?
Now that you can wipe data, you can factory reset and either Odin the stock tar or flash CM.
If you prefer to take least intrusive approach, try going into recovery and delete cache and dalvik cache and reboot. If still not working, the factory reset. If still having camera issues, then decide if you want to go with stock tar in Odin again or CM a clean install; wipe user data first.
Personally, I'd wipe everything except my titanium backups and go back to Odin stock tar and make sure stock works fully before going to CM. In a situation like you were in, I would have powered down, flashed the stock tar in Odin and let it auto boot. Flash the custom recovery so I could wipe everything and then power down again and flash the stock tar in Odin just to get a clean start with root and custom ROM.
Edit- what is camera connection error? Oh, I see; lost camera. New thread. Maybe someone on CM can help you.
Hello good people.
Just got my new G3 (D855) a couple of days ago. Great phone! First thing I did was to update the phone to stock android 5.0. Thought I would give it a try before i rooted the phone.. I decided to root the phone anyway, but now I can't seem to get TWRP (ver. 2.8.5.0) working. After pressing "reboot" after flashing (Flashify app) the screen goes black and the LED starts blinking red and blue.. I'm pretty new to the game, only rooted two times earlier... Does this error have something to do with the Lollipop upgrade? Very grateful for all your help
http://forum.xda-developers.com/lg-g3/help/secure-booting-error-cause-boot-t3064431
Same problem as me. Before it starts flashing it displays the error i posted.
If you want to boot it normally remove any power source and then boot it again.
Hunting Rifle said:
http://forum.xda-developers.com/lg-g3/help/secure-booting-error-cause-boot-t3064431
Same problem as me. Before it starts flashing it displays the error i posted.
If you want to boot it normally remove any power source and then boot it again.
Click to expand...
Click to collapse
Not good... There must be some sort of soultion? Did you upgrade the stock firmware to 5.0 before installing twrp on the phone?
anyong! said:
Hello good people.
Just got my new G3 (D855) a couple of days ago. Great phone! First thing I did was to update the phone to stock android 5.0. Thought I would give it a try before i rooted the phone.. I decided to root the phone anyway, but now I can't seem to get TWRP (ver. 2.8.5.0) working. After pressing "reboot" after flashing (Flashify app) the screen goes black and the LED starts blinking red and blue.. I'm pretty new to the game, only rooted two times earlier... Does this error have something to do with the Lollipop upgrade? Very grateful for all your help
Click to expand...
Click to collapse
Hunting Rifle said:
http://forum.xda-developers.com/lg-g3/help/secure-booting-error-cause-boot-t3064431
Same problem as me. Before it starts flashing it displays the error i posted.
If you want to boot it normally remove any power source and then boot it again.
Click to expand...
Click to collapse
Use this Auto - Script :- http://forum.xda-developers.com/showthread.php?t=3048845 By @topet2k12001 to install TWRP. Thread explains where you are going wrong and need to Downgrade "aboot" to KitKat for TWRP to work.....
Hi.
TWRP does not work with STOCK Lollipop yet. Do not even try it will not work. Wait a little bit more...
engcristiano said:
Hi.
TWRP does not work with STOCK Lollipop yet. Do not even try it will not work. Wait a little bit more...
Click to expand...
Click to collapse
Firstly: TWRP is a recovery image, which has nothing to do with whatever system ROM you are using!
What you want to do is to replace the LG stock recovery image with TWRP. This is done by writing the new image onto the recovery image memory location, which is found below.
Code:
[email protected]:/ $ ls -la /dev/block/platform/msm_sdcc.1/by-name|grep recovery
ls -la /dev/block/platform/msm_sdcc.1/by-name|grep recovery
lrwxrwxrwx root root 1970-05-08 09:48 recovery -> /dev/block/mmcblk0p20
1|[email protected]:/ $ ls -la /dev/block/mmcblk0p20
ls -la /dev/block/mmcblk0p20
brw------- root root 179, 20 1970-05-08 09:48 mmcblk0p20
As you can see, the flags are set to (u+rw) - so you would definitely need to get root access in order to overwrite to the current recovery partition on your device. As far as I know (at the 28th of March), you simply have to revert back to Kitkat in order to root your device. After succeded with that, I recommend the PurpleDrake-Lite root method, which worked flawlessly on my D855.
You can download an official version from the TWRP developers here which I installed (2.8.6.0) or use this version, which I cannot confirm to work. Both pages have their own instructions on properly installing their images.
After you have replaced the recovery image with TWRP, you are set to go with any Lollipop ROM. TWRP has a built in root enabling feature which starts before exiting a ROM installation.
Good luck!
k02a said:
Firstly: TWRP is a recovery image, which has nothing to do with whatever system ROM you are using!
What you want to do is to replace the LG stock recovery image with TWRP. This is done by writing the new image onto the recovery image memory location, which is found below.
Code:
[email protected]:/ $ ls -la /dev/block/platform/msm_sdcc.1/by-name|grep recovery
ls -la /dev/block/platform/msm_sdcc.1/by-name|grep recovery
lrwxrwxrwx root root 1970-05-08 09:48 recovery -> /dev/block/mmcblk0p20
1|[email protected]:/ $ ls -la /dev/block/mmcblk0p20
ls -la /dev/block/mmcblk0p20
brw------- root root 179, 20 1970-05-08 09:48 mmcblk0p20
As you can see, the flags are set to (u+rw) - so you would definitely need to get root access in order to overwrite to the current recovery partition on your device. As far as I know (at the 28th of March), you simply have to revert back to Kitkat in order to root your device. After succeded with that, I recommend the PurpleDrake-Lite root method, which worked flawlessly on my D855.
You can download an official version from the TWRP developers here which I installed (2.8.6.0) or use this version, which I cannot confirm to work. Both pages have their own instructions on properly installing their images.
After you have replaced the recovery image with TWRP, you are set to go with any Lollipop ROM. TWRP has a built in root enabling feature which starts before exiting a ROM installation.
Good luck!
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=3056951 is an excellent One-Click-Script, by @avicohh, which makes things easier when "Rooting" KitKat/Lollipop Firmwares. The OP then points you to @topet2k12001 's splendid "Auto-Script, http://forum.xda-developers.com/showthread.php?t=3048845, for installing TWRP Recovery.....
Just replacing the Recovery Image, by ADB or a Tool like Flashify, on a LG Lollipop System, will not work. The Lollipop aboot.img (Android Bootloader) must first be Downgraded to a "Signed" (Bump-ed) KitKat aboot.img. The above Thread by @topet2k12001 explains this in both Layman's Terms and Detail.....