Related
Hello everyone,
My problem is this: I wanted to install a CM10 nightly on the device, so I root using the DebugfsRoot method, install rom manager, flash a recovery, try to install a ROM and it did not work. Rebooting into recovery got me the red triangle, but using the volume buttons allowed me to get in (only it did not have the option to install updates or anything. I think it was just he mounting and partition options)
Since I did not unlock the device before doing this, I chose to do so using ASUS's unlock utility. Once done, I tried booting into recovery, but the device would be stuck at "booting recovery kernel image" and won't budge. I tried flashing different version of CW but it did not seem to work.
Finally, for some reason, I chose the "wipe data" option from the bootloader and the device was stuck, again, at "booting recovery kernel image", only this time I can't boot into a ROM nor can I boot back into bootloader.
What happens when I boot using power and volume down is this:-
The device is Unlocked
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Checking for android ota recovery
Booting recovery kernel image
and then everything's stuck.
Booting normally makes the device stop at "the device is unlocked" message because, I assume, there is no ROM flashed into the device.
Thanks for helping in advance.
It's not just that I can't get the unit to go into recovery, It's that I can't even get to fastboot (it tries to go into recovery every time I try to get into fastboot)
ShiroiKage said:
It's not just that I can't get the unit to go into recovery, It's that I can't even get to fastboot (it tries to go into recovery every time I try to get into fastboot)
Click to expand...
Click to collapse
I believe your device is bricked. Using a wrong version of custom recovery may caused this. I haven't seen anyone able to fix the issue that you having right now, the only thing is to send out to Asus for repair.
buhohitr said:
I believe your device is bricked. Using a wrong version of custom recovery may caused this. I haven't seen anyone able to fix the issue that you having right now, the only thing is to send out to Asus for repair.
Click to expand...
Click to collapse
So, if I get it repaired/replaced, what version of CW recovery should I get? It seems that there is not, yet, a version for the Infinity tab. I really want to get a custom ROM because the stuff ASUS has slapped on their version of Android gets under my skin.
ShiroiKage said:
So, if I get it repaired/replaced, what version of CW recovery should I get? It seems that there is not, yet, a version for the Infinity tab. I really want to get a custom ROM because the stuff ASUS has slapped on their version of Android gets under my skin.
Click to expand...
Click to collapse
The Team Win TWRP version 2.3.1.0 works really well. It's a touch recovery and very easy to use and full featured.
okantomi said:
The Team Win TWRP version 2.3.1.0 works really well. It's a touch recovery and very easy to use and full featured.
Click to expand...
Click to collapse
One very last question:-
Would it work if I get the CM10 nightly for the TF300T installed on a TF700T (since it's practically the same device with a different screen)? If not, is there a ROM that's pure JB without ASUS's stuff installed one it?
Your replies are very much appreciated.
ShiroiKage said:
One very last question:-
Would it work if I get the CM10 nightly for the TF300T installed on a TF700T (since it's practically the same device with a different screen)? If not, is there a ROM that's pure JB without ASUS's stuff installed one it?
Your replies are very much appreciated.
Click to expand...
Click to collapse
I would NOT recommend you do so with tf300 on tf700. There is no pure stock debloated version for JB, however, if you want to stay as close as stock and stable I would recommend "Cleanrom for JB". This rom doesn't have Asus bloatware and a few performance tweaks make it very good.
buhohitr said:
I would NOT recommend you do so with tf300 on tf700. There is no pure stock debloated version for JB, however, if you want to stay as close as stock and stable I would recommend "Cleanrom for JB". This rom doesn't have Asus bloatware and a few performance tweaks make it very good.
Click to expand...
Click to collapse
So I got it replaced (Best Buy swapped it for a new one) and everything's fine. I even installed Clean ROM and it's good. Problem is that the left speaker is not working and I need to flash the stock ROM to make sure it's nothing caused by software, before I go back and re-return the unit. However, ASUS's firmware is not longer wanting to flash. It gives me the "failed" message in TWR's recovery (no backup because my internal memory was wiped when installing ASUS's JB update :/)
EDIT: Never mind. I thought the holes at the bottom, on either side of the USP port, were the speakers. Turns out I was not thinking straight. Still, I'd like to know if anyone has an idea as to why the ASUS firmware is not wanting to install.
ShiroiKage said:
So I got it replaced (Best Buy swapped it for a new one) and everything's fine. I even installed Clean ROM and it's good. Problem is that the left speaker is not working and I need to flash the stock ROM to make sure it's nothing caused by software, before I go back and re-return the unit. However, ASUS's firmware is not longer wanting to flash. It gives me the "failed" message in TWR's recovery (no backup because my internal memory was wiped when installing ASUS's JB update :/)
EDIT: Never mind. I thought the holes at the bottom, on either side of the USP port, were the speakers. Turns out I was not thinking straight. Still, I'd like to know if anyone has an idea as to why the ASUS firmware is not wanting to install.
Click to expand...
Click to collapse
You can't install the ASUS firmware through custom recovery. It has to be stock. I believe there are signature checks that prevent it from installing otherwise.
Sent from my ASUS Transformer Pad TF700T
did you unzip the file? should be a zip within a zip. you flash the zip inside
lafester said:
did you unzip the file? should be a zip within a zip. you flash the zip inside
Click to expand...
Click to collapse
You know, I unzipped the file the first time I installed it to get Clean ROM to flash, I had the unzipped folder there yet I managed to forget to use the unzipped file. /InfiniteFacePalm
Hi all,
After having successfully rooted my TF700 lately (while keeping the bootloader locked), I've been looking into unlocking the bootloader so I can flash a custom ROM (thinking about CROMI). Before flashing a custom ROM, people seem to recommend getting nvflash in order.
My problem is, however, I'm already on JB, and my understanding is that you need an ICS .26 bootloader (or earlier) in order to setup nvflash. I know that it's possible to downgrade the firmware from JB to ICS (in fact, this is what I did in order to be able to root my device - going from the latest JB to ICS .30); however, after searching around a fair bit, I'm still not clear on whether it's possible to revert the bootloader to an earlier version.
Can someone please clarify this for me. If I've already updated my device to JB, is there absolutely no way for me to set up nvflash?
Thanks!
joshnl said:
Hi all,
After having successfully rooted my TF700 lately (while keeping the bootloader locked), I've been looking into unlocking the bootloader so I can flash a custom ROM (thinking about CROMI). Before flashing a custom ROM, people seem to recommend getting nvflash in order.
My problem is, however, I'm already on JB, and my understanding is that you need an ICS .26 bootloader (or earlier) in order to setup nvflash. I know that it's possible to downgrade the firmware from JB to ICS (in fact, this is what I did in order to be able to root my device - going from the latest JB to ICS .30); however, after searching around a fair bit, I'm still not clear on whether it's possible to revert the bootloader to an earlier version.
Can someone please clarify this for me. If I've already updated my device to JB, is there absolutely no way for me to set up nvflash?
Thanks!
Click to expand...
Click to collapse
Once you're on JB, the lowest you can downgrade is ICS .30. You're too late for Nvflash. No way around it.
Okay... sucks, but thanks for the info. That's what I was afraid of.
Since that is the case, how critical is it to set up nvflash before getting into the whole custom ROM thing? Am I crazy to get into it without nvflash as a backup plan?
joshnl said:
Since that is the case, how critical is it to set up nvflash before getting into the whole custom ROM thing? Am I crazy to get into it without nvflash as a backup plan?
Click to expand...
Click to collapse
There is a bug in the bootloader that you should be aware of: If your recovery is broken because it is
* too old, designed for the ICS bootloader, or
* you erased it via fastboot
then you should NEVER EVER choose "wipe data" from the bootloader menu. Except you want an expensive paperweight. Because then you can't even enter fastboot to fix it. This is the only situation where nvflash would really help you out.
If you always test any newly flashed recovery first by using the power+volume buttons, you are safe.
Thanks, _that!
_that said:
There is a bug in the bootloader that you should be aware of: If your recovery is broken because it is
* too old, designed for the ICS bootloader, or
* you erased it via fastboot
then you should NEVER EVER choose "wipe data" from the bootloader menu. Except you want an expensive paperweight. Because then you can't even enter fastboot to fix it. This is the only situation where nvflash would really help you out.
If you always test any newly flashed recovery first by using the power+volume buttons, you are safe.
Click to expand...
Click to collapse
I know man who did wipe data from bootloader, it didn't brick him He has done this today on unlocked, TWRP and CROMI on TF300T. The newest bootloader fix it.
Hazard17 said:
I know man who did wipe data from bootloader, it didn't brick him He has done this today on unlocked, TWRP and CROMI on TF300T. The newest bootloader fix it.
Click to expand...
Click to collapse
It would not brick him if he installed the latest version the either recovery -- that's exactly what _that said.
Simply put, just keep your recovery up-to-date when major versions release and update the bootloader. When things such as this happen, they will be posted in the rom threat, just make sure you read thoroughly. Also, read the change log before upgrading the recovery, and if you use TWRP use GooManager and it will upgrade it for you at a tap of a button.
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The stock Asus firmware includes bootloader, kernel, recovery and apps. You have flashed the stock recovery. Head over to the twrp thread or my ROM thread in my sig to see how to get twrp 2.5 onto your tab.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
Yes, you did. Everytime you install stock file of any version, it will update your bootloader, rom, and kernel. Just use Motochopper to root your device and reinstall your custom recovery with goomanager.
No, it is stock recovery. Just reroot with motochopper and install custom recovery with goomanager. Have fun. :good:
Right, thanks! If I want to stay completely stock I just need to figure out why the newer update is failing. Could be the file name now I think about it.
Otherwise I'll re-root and re-TWRP...
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The Android on his back is your stock recovery and it does not find a valid update file.
Weird is, that your system seems to see the 10.6.1.14 file (I assume you get an automatic notification and click "install" or "update" ) and then the recovery does not seem to install it...?
You could have a bad download, so try that first if you want to get the latest stock rom, or you can try to rename the downloaded file to EP201_768_SDUPDATE.zip, put it on your microSD card and reboot into recovery. The recovery should recognize the update file and start flashing it.
But since you are unlocked anyway - why don't you give CromiX a try? It runs so much better than the stock rom!
And for that, yes you would have to root again using the Motochopper tool and then install TWRP 2.5 with Goo Manager.
If you go that route make sure you flash the latest bootloader from the OP of the CROMiX thread first, boot back into your old rom once before you flash CROMiX.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Anatosuchus said:
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Click to expand...
Click to collapse
It's based on the stock rom, cleaned up and tweaked and optimized. Everything works - and better than on stock! I recommend selecting the option to disable fsync during installation. It boosts performance considerably, and since the rom is totally stable, the "risk" is neglible.
You will love it!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
OK, ChromiX installed! Looks interesting already, will tinker with it over the next couple of days.
What are my alternatives now?
Previously I was running CleanRom7 – but somehow must taken enough of update to somehow have locked the bootloader:
I’m currently running a “official Samsung” version that is 4.1.2.
I can do the following:
• Flash Root
• Flash a new recovery – used the latest CWM version 2.6.3.1
• Any attempt to either flash the latest ML1 or old CleanRom7 don’t successfully boot.
• At that point I can ODIN back to the 4.1.2 official Samsung version
The download screen looks like this:
Product Name: ICH-I535
Custom Binary Download: Yes (2 count)
Current Binary: Samsung Official
System Status: Official
Qualcom Secureboot: Enable
I’m constantly getting asked by some app if I want to do the OTA upgrade, I have been postponing for 1 hour
Question is given these 2 alternatives, what are the opinions to these two questions:
At this point should I just either ODIN or flash the latest ML1 upgrade and then root?
Or
Stay on 4.1.2?
bgbird said:
What are my alternatives now?
Previously I was running CleanRom7 – but somehow must taken enough of update to somehow have locked the bootloader:
I’m currently running a “official Samsung” version that is 4.1.2.
I can do the following:
• Flash Root
• Flash a new recovery – used the latest CWM version 2.6.3.1
• Any attempt to either flash the latest ML1 or old CleanRom7 don’t successfully boot.
• At that point I can ODIN back to the 4.1.2 official Samsung version
The download screen looks like this:
Product Name: ICH-I535
Custom Binary Download: Yes (2 count)
Current Binary: Samsung Official
System Status: Official
Qualcom Secureboot: Enable
I’m constantly getting asked by some app if I want to do the OTA upgrade, I have been postponing for 1 hour
Question is given these 2 alternatives, what are the opinions to these two questions:
At this point should I just either ODIN or flash the latest ML1 upgrade and then root?
Or
Stay on 4.1.2?
Click to expand...
Click to collapse
Ok, The question is, do you still want to flash custom rom/kernel?? If you do and since you're still on 4.1.2 you still can unlock the bootloader and flash custom 4.3 rom (with unlocked bootloader) for the 4.3 experience/look & feel.
More info
buhohitr said:
Ok, The question is, do you still want to flash custom rom/kernel?? If you do and since you're still on 4.1.2 you still can unlock the bootloader and flash custom 4.3 rom (with unlocked bootloader) for the 4.3 experience/look & feel.
Click to expand...
Click to collapse
I'd like a custom rom - but when I tried to flash the ML4.3 offered on this site - or even tried to reflash my old Cleanrom7 that i still had on my external flash memory that previously worked I couldn't boot.
I flashed VRUCML1_Stock_Root_Deodex (12.31.13 downloaded from the link. MD5 checked OK) this would try to boot - then just go back into recovery (I used the latest version of TWRP and used EZ-Unlock). Of course I wiped the device before I started. I flashed the rom and observed all of the successful messages during the flash. I never caught the really little blue message that flashed at the beginning of the boot cycle before it went black and rebooted to recovery. At that point I wiped again and flashed Cleanrom 7. It flashed, then started the installer that let me pick all sorts of apps. When I tried to boot - it just hung on the Samsung SIII banner that appears shortly after boot. I let it sit there for about an hour before pulling the battery. Then I ODINed back the the 4.1.2 version that I'm running now.
I tried this several times - even going as far as installing CRP recovery - same result.
So I'm about our of ideas...
bgbird said:
I'd like a custom rom - but when I tried to flash the ML4.3 offered on this site - or even tried to reflash my old Cleanrom7 that i still had on my external flash memory that previously worked I couldn't boot.
I flashed VRUCML1_Stock_Root_Deodex (12.31.13 downloaded from the link. MD5 checked OK) this would try to boot - then just go back into recovery (I used the latest version of TWRP and used EZ-Unlock). Of course I wiped the device before I started. I flashed the rom and observed all of the successful messages during the flash. I never caught the really little blue message that flashed at the beginning of the boot cycle before it went black and rebooted to recovery. At that point I wiped again and flashed Cleanrom 7. It flashed, then started the installer that let me pick all sorts of apps. When I tried to boot - it just hung on the Samsung SIII banner that appears shortly after boot. I let it sit there for about an hour before pulling the battery. Then I ODINed back the the 4.1.2 version that I'm running now.
I tried this several times - even going as far as installing CRP recovery - same result.
So I'm about our of ideas...
Click to expand...
Click to collapse
When you flashed back to 4.1.2 and it's working fine, at this point check to see if your bootloader is unlocked (even unlock tool said unlocked, you need to verify that it's unlocked). If it's not what ever you flash will not work.
buhohitr said:
When you flashed back to 4.1.2 and it's working fine, at this point check to see if your bootloader is unlocked (even unlock tool said unlocked, you need to verify that it's unlocked). If it's not what ever you flash will not work.
Click to expand...
Click to collapse
I never "flash" back. I have an ODIN image (KIES_HOME_I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 ) that I use. At that point everything is replaced and I'm back to a stock bootloader (at least that's how it looks to me). When I root - then use EZ-Unlock at this point, the bootloader is locked. I suppose that it would be interesting to try to "flash" a 4.1.2 original and see what would happen.
bgbird said:
I never "flash" back. I have an ODIN image (KIES_HOME_I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 ) that I use. At that point everything is replaced and I'm back to a stock bootloader (at least that's how it looks to me). When I root - then use EZ-Unlock at this point, the bootloader is locked. I suppose that it would be interesting to try to "flash" a 4.1.2 original and see what would happen.
Click to expand...
Click to collapse
I believe your image is fine. The key I want to point out is make sure your bootloader is unlocked. After you unlock with EZ-Unlock, boot into download mode and verify that the bootloader is actually unlock, before you proceed to flash anything else.
buhohitr said:
I believe your image is fine. The key I want to point out is make sure your bootloader is unlocked. After you unlock with EZ-Unlock, boot into download mode and verify that the bootloader is actually unlock, before you proceed to flash anything else.
Click to expand...
Click to collapse
OK - I'll try that. What do I look for in download mode that would indicate (or what should I try to do) that would prove that I'm "unlocked"?
boot into Odin mode (download mode) and you shoud see.
buhohitr said:
boot into Odin mode (download mode) and you shoud see.
Click to expand...
Click to collapse
I don't see anything about "unlocked"
when i press the down volume, home and power button I start into ODIN mode.
if i press the down arrow the phone will just re-boot
then i press the up arrow to continue into ODIN (download mode) I get:
:
Product Name: ICH-I535
Custom Binary Download: Yes (3 count)
Current Binary: Customl
System Status: Customl
Qualcom Secureboot: Enable
I still don't see anything about the unlocked bootloader
bgbird said:
I don't see anything about "unlocked"
when i press the down volume, home and power button I start into ODIN mode.
if i press the down arrow the phone will just re-boot
then i press the up arrow to continue into ODIN (download mode) I get:
:
Product Name: ICH-I535
Custom Binary Download: Yes (3 count)
Current Binary: Customl
System Status: Customl
Qualcom Secureboot: Enable
I still don't see anything about the unlocked bootloader
Click to expand...
Click to collapse
This Qualcom Secureboot: Enable - meaning bootloader is locked
buhohitr said:
This Qualcom Secureboot: Enable - meaning bootloader is locked
Click to expand...
Click to collapse
Just as a matter of curiosity, EZ-Unlock reports the bootloader to be “unlocked”. Wonder what’s wrong with that?
So pretty much at this point it appears that the only thing that I can do is to ODIN the official 4.3 tar file or stay on the 4.1.2 file that I ODINed previously.
bgbird said:
Just as a matter of curiosity, EZ-Unlock reports the bootloader to be “unlocked”. Wonder what’s wrong with that?
So pretty much at this point it appears that the only thing that I can do is to ODIN the official 4.3 tar file or stay on the 4.1.2 file that I ODINed previously.
Click to expand...
Click to collapse
Are you rooted? if not it's not going to work.
buhohitr said:
This Qualcom Secureboot: Enable - meaning bootloader is locked
Click to expand...
Click to collapse
I am rooted - I'm sure of that...
I'm also running the latest TWRP recovery.
EZ-Unlock still lets me lock and unlock the bootloader.
I'm also thinking of flashing VRLE6.bootloader.zip, rebooting, doing an EZ-Unlock and seeing what happens.
If that doesn't work - I'll have to decide
1. do I f staying where I'm at - running 4.1.2 ?
or
2. Do I give up and take the softbrick tar file and lock everything up ?
I'm not sure of what are the pros and cons of either alternative
bgbird said:
EZ-Unlock still lets me lock and unlock the bootloader. I'm also thinking of flashing VRLE6.bootloader.zip, rebooting, doing an EZ-Unlock and seeing what happens.
If that doesn't work - I'll have to decide
1. do I f staying where I'm at - running 4.1.2 ?
or
2. Do I give up and take the softbrick tar file and lock everything up ?
I'm not sure of what are the pros and cons of either alternative
Click to expand...
Click to collapse
If you're not rooted, EZ unlock just report false results.
If you like to play with custom rom/kernel, meaning not bug free and become a flashcoholic then stay with 4.1.2
If you want a stable, no headache trouble free then upgrade to 4.3
I upgraded my wife to 4.3 and very happy with the results. Everything just work, performance is very good and smooth, gps locked in seconds...enough said.
buhohitr said:
If you're not rooted, EZ unlock just report false results.
If you like to play with custom rom/kernel, meaning not bug free and become a flashcoholic then stay with 4.1.2
If you want a stable, no headache trouble free then upgrade to 4.3
I upgraded my wife to 4.3 and very happy with the results. Everything just work, performance is very good and smooth, gps locked in seconds...enough said.
Click to expand...
Click to collapse
Even if I had to stay on 4.1.2 I'd want CleanRom7 at least. I used that since July when it came out. I liked the features and customizations. I'd like to continue to flash - however every time that I try ( and you can see the results earlier in the thread) the phone wouldn't boot. I think that some part of the OTA got on the phone. For a period of time, I was constantly nagged to take the upgrade. I think that my son answered "yes" and some part updated - until stopped Cleanrom.
Anyway I tried to reflash CleanRom as well as the non-locked ML1 item. Each time, Samsung flashes, then the ornamental Samsung SIII graphic just sits there. In a normal boot, that only lasts a second. Maybe I'll try it again and let sit there for an hour or two and see if something changes.
bgbird said:
Even if I had to stay on 4.1.2 I'd want CleanRom7 at least. I used that since July when it came out. I liked the features and customizations. I'd like to continue to flash - however every time that I try ( and you can see the results earlier in the thread) the phone wouldn't boot. I think that some part of the OTA got on the phone. For a period of time, I was constantly nagged to take the upgrade. I think that my son answered "yes" and some part updated - until stopped Cleanrom.
Anyway I tried to reflash CleanRom as well as the non-locked ML1 item. Each time, Samsung flashes, then the ornamental Samsung SIII graphic just sits there. In a normal boot, that only lasts a second. Maybe I'll try it again and let sit there for an hour or two and see if something changes.
Click to expand...
Click to collapse
If you are switch from rom to rom, you may have trash residuals. I would wipe cache/dalvik cache/data/system before I flash another rom (clean install), saved me a lot of little issues here and there...
buhohitr said:
If you are switch from rom to rom, you may have trash residuals. I would wipe cache/dalvik cache/data/system before I flash another rom (clean install), saved me a lot of little issues here and there...
Click to expand...
Click to collapse
Formatting your internal SD may also be needed, because 4.3 creates a 0/ folder that 4.1 doesn't have.
Alternatively, philz touch recovery has a 0/folder migration that will clear out that folder when switching.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Formatting your internal SD may also be needed, because 4.3 creates a 0/ folder that 4.1 doesn't have.
Alternatively, philz touch recovery has a 0/folder migration that will clear out that folder when switching.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
two questions?
1. Do you have a link for philz touch recovery?
2. If I format the internal SD - will an nandroid backup still work? I thought that that had to back into an identical file structure...
Also I do a factory reset each time that I flash.
I know that I'm root because EZ-Unlock requires it. If root isn't enabled - it terminates. When Root is enabled, SuperSU asks permission to do the unlock
bgbird said:
two questions?
1. Do you have a link for philz touch recovery?
2. If I format the internal SD - will an nandroid backup still work? I thought that that had to back into an identical file structure...
Click to expand...
Click to collapse
1.
http://forum.xda-developers.com/showthread.php?t=2588639
2. No, The file structure gets completely replaced because a nandroid copies your internal sd card. It'll remake the folder structure.
Sent from my SCH-I535 using Tapatalk 2
Just a quick question to cover all the bases. Which version of EZ Unlock are you using? Version 1.2 is the only one that actually works to unlock your bootloader.
Hey guys,
I was previously on xtresolite 2.4 lollipop rom and saw that he had a new rom out based on Marshmellow 6.01.
The instructions for the installation the new rom said to flash the new bootloader, modem and recovery before installing the new rom.
I flashed the bootloader with Odin using the BL button as instructed and how it's stuck on the Samsung Screen. I can still boot into download mode, but that's about it. It won't let me boot into recovery. Doing a bit of research it says to boot into download warning screen and cancel. Then quickly do the recovery buttons (volup, home, power), but it still won't go in.
So now I'm stuck! i'm trying to download the new stock Marshmellow firmware to see if I can install that, but aside from that I'm not sure what else I can do.
Any suggestions? Since I'm still able to use Odin, can I try to re-install the correct bootloader or is that too late? I'm not even sure which bootloader to install now. :crying::crying::crying:
Any help is much appreciated!
Thanks,
kc
as long as you can boot into the download mode, everything's alright. try flashing the latest stock rom for your model. then a new recovery, and then the new xtrestolite rom.
if something fails. do it again.... flash the latest stock rom, and so on.
Just make sure you have the correct model software for your phone and there won't be any issues. Did you backup your imei way back when you rooted on lollipop? If you did then everything will be fine if you didn't, Restore stock ROM and root, then backup your imei, hopefully you won't have any issues with your modem
Try pressing on power + vol down untill the phone shuts down then quickly press home+power+vol up before the phone starts . you will be in recovery try a factory reset then wait for the first boot. Voila !
hey all, just wanted to update. I still couldn't get into recovery, but was able to flash the stock rom and it's working as stock right now. Been using it for the past week or so and no major issues noted. I'm a bit scared to mess around again
Now that I'm on stock Marshmallow 6.0.1 rom, do I still need to try and flash the modem and boot loader for it?
Also, now that i'm on stock do I need to unroot again to install the twrp recovery? or can I just go into odin and flash it right away?
Thanks again for the help and suggestions!!!
tnimk said:
hey all, just wanted to update. I still couldn't get into recovery, but was able to flash the stock rom and it's working as stock right now. Been using it for the past week or so and no major issues noted. I'm a bit scared to mess around again
Now that I'm on stock Marshmallow 6.0.1 rom, do I still need to try and flash the modem and boot loader for it?
Also, now that i'm on stock do I need to unroot again to install the twrp recovery? or can I just go into odin and flash it right away?
Thanks again for the help and suggestions!!!
Click to expand...
Click to collapse
Stock rom overrides everything so your root is long gone & you now have the latest bootloader & modem already - don't stress & no need to do anything else! If you want custom recovery simply flash with latest TWRP using Odin in download mode (in tar format using AP button). Don't root with TWRP if asked to - instead download latest recovery flash-able SuperSU (ZIP) onto your device & then flash it using TWRP. This will be the safest option for you (with root if you want).
AFAIK one always uses the "AP" button if you wanna flash <anything> with Odin - not the BL button (I've never used this). The rest are for pro's only (of which I'm not one). I'm simply a regular rom flasher & read/study/compare several guides before attempting anything I've never done before with my device. If the overall feeling is not a good one, rule of thumb is I don't proceed until I feel confident enough about what I'm attempting to do.
Good luck.
On my sm-G920I
I flashed the xtresolite ROM without first flashing the bootloader and modem and it worked fine for me, if you back up everything with an otg cable onto a USB then flash the ROM everything should work fine but you will have to wait around 5 minutes for it to boot. If your still waiting after 10-20 minutes then you did something wrong and you can just wipe your entire phone then recover everything from your backup on your USB ????????