Related
Hi guys, having some serious issues with my Tab. It's the Telstra GT-P7320T.
So I had it rooted and flashed with the glitkis kernel all working fine still on the standard Telstra version of honeycomb. Then when their update for ICS finally came out (after nearly 6 months of knocking it back) I went to update it in the normal manner, not thinking it would have a hissy fit with the root and the custom kernel.
So after it downloaded it did its pre install bit, it rebooted, but then loaded into CWM recovery, and thats where its stayed. I've tried factory resets, clearing and formatting all the caches (davlik, system etc) i've used adb to push a few different roms and kernels etc to the device but nothing ive tried has worked. I flashed arlics ics rom, but it still just boots into recovery. Ive tried flashing the stock kernel and stock recovery but when i try to install zip from sd them they fail "install aborted (bad)"
Anyone got any ideas on what process and files I should try? Ive searched up and down the forum trying different methods for fixing soft brick and returning to stock but to no avail.
Cheers
ragvaror said:
Hi guys, having some serious issues with my Tab. It's the Telstra GT-P7320T.
So I had it rooted and flashed with the glitkis kernel all working fine still on the standard Telstra version of honeycomb. Then when their update for ICS finally came out (after nearly 6 months of knocking it back) I went to update it in the normal manner, not thinking it would have a hissy fit with the root and the custom kernel.
So after it downloaded it did its pre install bit, it rebooted, but then loaded into CWM recovery, and thats where its stayed. I've tried factory resets, clearing and formatting all the caches (davlik, system etc) i've used adb to push a few different roms and kernels etc to the device but nothing ive tried has worked. I flashed arlics ics rom, but it still just boots into recovery. Ive tried flashing the stock kernel and stock recovery but when i try to install zip from sd them they fail "install aborted (bad)"
Anyone got any ideas on what process and files I should try? Ive searched up and down the forum trying different methods for fixing soft brick and returning to stock but to no avail.
Cheers
Click to expand...
Click to collapse
hey mate,
i was just caught out by this last night. all you need to do is re-flash on a stock rom with ether oden of heimdall and youre good to go. im sure there is a oden flashable rom on these forums
take it sleazy!
Cheers mate,
Ive been trying to reflash a stock rom by pushing it to the sd card and installing it, but when i go to install it from recovery it tells me the rom file is bad and aborts, like its corrupt or something, so maybe i need to find some different downloads to try. Thanks, there's hope still at least, lol. I'll find the odin file and try doing it that way.
ragvaror said:
Cheers mate,
Ive been trying to reflash a stock rom by pushing it to the sd card and installing it, but when i go to install it from recovery it tells me the rom file is bad and aborts, like its corrupt or something, so maybe i need to find some different downloads to try. Thanks, there's hope still at least, lol. I'll find the odin file and try doing it that way.
Click to expand...
Click to collapse
yeah, i think its becaute the cwm recovery doesnt know what to do with the update.
you need to have the stock recovery installed. dont take my word for it though.
just look up a tutorial for flashing a rom via oden. its really easy, just make sure the image you are flashing is of .tar.md5 extension.
You can get the stock rom at sammobile.com. down load the zip file then extract the .tar.md5 file out of it using 7-zip.
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round
FIXED!! - Cheers Everyone!
OK, so I downloaded the stock telstra rom off the forum here, its at the top of page 3 at present, flashed that with Oden, which fixed the soft brick and allowed me to boot again. I then flashed the stock recovery, rebooted, got into the system and downloaded the ICS update again. Once it rebooted, with the stock recovery it was able to install and successfully boot into ICS!! I was more stoked than I've ever been before, let me tell you, lol.
how ?
ragvaror said:
FIXED!! - Cheers Everyone!
OK, so I downloaded the stock telstra rom off the forum here, its at the top of page 3 at present, flashed that with Oden, which fixed the soft brick and allowed me to boot again. I then flashed the stock recovery, rebooted, got into the system and downloaded the ICS update again. Once it rebooted, with the stock recovery it was able to install and successfully boot into ICS!! I was more stoked than I've ever been before, let me tell you, lol.
Click to expand...
Click to collapse
i currently have the same problem as you did, how did you flash with odin if you're stuck in recovery mode ?
please help, I'm racking my brain trying to figure this out.
Title pretty much says it all. I've got myself in a pickle. I've manually downloaded the 4.3 OTA. Do I rename it or keep it as is? Right now it's called OTA_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.04.651.2-1.31.651.2_release_335437r9p4z0zrva4gqsfs.zip
I'm about to install the stock recovery as soon as I'm done pushing this huge OTA file onto /sdcard.
What do I do from here?
I renamed the OTA update.zip and flashed the stock recovery. Stock recovery is telling me unable to mount sdcard. What the crap.
There is an option to install from SD Card and one for internal storage in the stock recovery. Choose the internal storage option and then navigate to your update.zip.
NOTE: You really ought to not only be on the stock recovery, but the stock ROM as well. The update doesn't usually contain a full /system to flash, just a few files and some patches to existing files.
kalaker said:
There is an option to install from SD Card and one for internal storage in the stock recovery. Choose the internal storage option and then navigate to your update.zip.
NOTE: You really ought to not only be on the stock recovery, but the stock ROM as well. The update doesn't usually contain a full /system to flash, just a few files and some patches to existing files.
Click to expand...
Click to collapse
I was S-Off and was going to go back to S-On and go back to fully locked, no tampered message, and all that. I think I went s-on THEN tried flashing the full 4.3 firmware, which I believe was my ultimate mistake. Watching it go through the steps, it looked like it installed about half, instead of the whole thing.
I'm sitting here on HBOOT 1.55 and have no idea if it looks the way it's supposed to. I unlocked the bootloader and flashed twrp and flashed back to OMJ's stock 4.3 rom, but I'm now S-ON with the newest HBOOT and no way to know if the entire 4.3 firmware truly installed all the way. What worries me is when I look at the HBOOT now there's some text in red that didn't use to be there that says "OS-1.29.651.10 (3.04.651.2)" Which is truly baffling me. I've never seen that before on the bootloader screen.
Ok, so I tried following the method described here:
http://forum.xda-developers.com/showthread.php?t=2712039
I was on JB. Installed SS 3.71, downloaded the odexed version of UrDroid and odin files.
Procedure I followed:
Booted into SS
Factory reset
Install urdroid - deodexed
Installation failed, zip wouldn't open
Booted back up, downloaded urdroid again - odexed version this time
pulled battery, booted to safestrap
factory reset
install new zip, worked this time
tried booting to download mode with vol down key, didn't work for some reason. just went to SS splash screen then tried to boot
pulled battery, booted SS again, used the reboot menu to get to download mode
followed steps to set up partitions in ODIN, seemed to work fine
Now when I try to boot it just shows me the SS splash screen, then when I let it boot it just goes to a black screen with a solid blue indicator LED.
Next, I tried to verify the MD5 on the UrDroid zip and it didn't match. I downloaded it again, copied it to my external SD, and it then checked out.
Wiped, installed, ran the odin stuff again. Same problem.
I'm guessing the next step is to restore it back to MJ5 using this method: http://forum.xda-developers.com/showthread.php?t=2559715&page=118
Except several of the files linked there are no longer available....
I'm feeling a little panicked now, this is my only phone lol. Can anyone give me a hand?
If you're on MJ5 and If you can access Safestrap recovery, this should work : http://forum.xda-developers.com/showthread.php?t=2619005
andygev35 said:
If you're on MJ5 and If you can access Safestrap recovery, this should work : http://forum.xda-developers.com/showthread.php?t=2619005
Click to expand...
Click to collapse
I thought that once you update to KK, you can't go back to JB... except I don't know if I ever completed the update. I'm not entirely sure how this process even works.
Do you flash the rom, and then the ODIN portion of it prepares your phone for KK?
Boot into safestrap recovery, click reboot, click reboot to recovery (which will boot you into system recovery). Near the top of the system recovery screen it will show you what version of firmware you have. If it's MJ5, then just do a restore within safestrap recovery to the restore files you get from the link I posted earlier.
andygev35 said:
Boot into safestrap recovery, click reboot, click reboot to recovery (which will boot you into system recovery). Near the top of the system recovery screen it will show you what version of firmware you have. If it's MJ5, then just do a restore within safestrap recovery to the restore files you get from the link I posted earlier.
Click to expand...
Click to collapse
First of all, thank you for your help.
In recovery, it just says "Android system recovery <3e>". Then goes down to the options you can select.
Before you posted, I tried installing a MJ5 custom rom (FireNote) in the stock slot and now it successfully boots. Which is certainly an improvement. I tried the same process again with UrDroid and had the same result as before - no boot. Now I'm back on FireNote again.
Since FireNote works fine, is it safe to conclude that the Odin process did not properly prepare my boot system for KitKat, and that is why the KK rom isn't working at all?
Have I stumped XDA?? Haha.
I went over the guide again and can't see anything that I've done wrong, but I certainly could have. Are there glitches in Odin3 with Windows 7 that I should be looking out for or anything?
Another thought: I was attempting to do this with SafeStrap 3.71 installed. I thought that 3.72 should be sideloaded after I had switched to KitKat. Was this incorrect? Should I have started by installing 3.72 in my JB rom?
Well, I just let out a string of bad words.
When I ran Odin it defaulted to my 'return to stock' files even though I ran it from a completely different folder... and I didn't realize it.
I'm guessing using the right files will resolve this problem.
Wow, I'm an idiot.
steveh_131 said:
Well, I just let out a string of bad words.
When I ran Odin it defaulted to my 'return to stock' files even though I ran it from a completely different folder... and I didn't realize it.
I'm guessing using the right files will resolve this problem.
Wow, I'm an idiot.
Click to expand...
Click to collapse
I wouldn't say you're an idiot. You're human!
**Make certain that your reactivation lock in security settings is off before beginning this process**
1. Take the OA1 OTA update.
2. Download and install Towelroot-v3.apk(this version does not require internet access).
3. Place your phone into "Download Mode" (press and hold the Home, Volume Down, and Power keys until the phone powers on and displays warning screen, then press Volume Up key) and flash the G900A_ND3_Stock_Kernel using Odin's PDA slot(AP in Odin v3.09+).
4. Open the Towelroot app from your app drawer and press "Make it Rain" to root your device.
5. Power off then boot into "Download Mode" again and flash the G900A_OA1_Stock_Kernel also using Odin's PDA slot(AP in Odin v3.09+).
6. Install SuperSU to manage root access. Done!
Changelog: http://www.att.com/esupport/article.jsp?sid=KB424848&cv=820&_requestid=1642069
Troubleshooting:
1. Should the OA1 ota update fail consider returning to factory stock NCE (all User Data will be lost) by flashing the G900A_Downgrade_to_NCE.tar using Odin's PDA slot(AP in Odin v3.09+) then taking the OTA updates to OA1. Or, place the G900A_NCE_to_NG3_OTA.zip and G900A_NG3_tA1_OTA.zip onto your ext-sdcard and sideload from stock recovery starting with the G900A_NCE_to_NG3_OTA.zip. Once updated to OA1 continue from Step 2 above.
2. When flashing the kernel the most common cause of an Odin flash failure is a bad usb port or cable. Please check before reporting a failure!
Notes:
1. The above process will not affect your User Data or Knox Warranty Flag.
2. After flashing the ND3 kernel your phone will run a little wonky and towelroot may not root on the first try. If that happens reboot and try towelroot once again. Once rooted and after flashing the OA1 kernel your phone will once again run like a champ!
Alternative Safestrap Method:
1. Place the G900A_OA1_100%_Stock_Rooted_ROM onto your ext-sdcard.
2. From Safestrap recovery press "Backup" and backup your User Data.
3. From the main menu press "Wipe" then perform an "Advanced Wipe" and wipe everything but your ext-sdcard.
4. Next, press "Install," then select and install the G900A_OA1_100%_Stock_Rooted_ROM.
5. Once complete, press "Restore" and restore your User Data.
6. Last, from the main menu press "Reboot," then "System." Done!
After following the above process your phone will pause on the AT&T splash screen for about 2 minutes before rebooting.
Optional - Enable Native Tethering AddOn:
1. Place the G900A_OA1_TetherAddOn.zip onto your external sd-card.
2. From Safestrap recovery flash the file using "Stock" Slot but do not wipe!
3. Reboot. Done!
Notes:
1. The above process will not affect your User Data or Knox Warranty Flag.
2. This process will update your Modem, Non-hlos, System, Kernel, Stock Recovery, and Bootloader to OA1 (BusyBox is also pre-installed).
3. The User Data "Backup" and "Restore" steps in the instructions are not mandatory but will greatly reduce your device's set-up time. All currently installed non-system apps and settings will be automatically restored.
Credits:
benwaffle - for his flashboot script allowing flashing of the OA1 kernel(built into the ROM) in Safestrap.
Awsome
Can someone post OTA . cfg file please.
norbarb said:
Can someone post OTA . cfg file please.
Click to expand...
Click to collapse
G900A_NG3_tA1_OTA.zip
muniz_ri said:
G900A_NG3_tA1_OTA.zip
Click to expand...
Click to collapse
Thank You
Does the NG3 OTA update zip break root?
Currently my phone is on NG3, Rooted with wannam xposed installed. Also I have frozen multiple apps. Is there a way to remove Root and cleanup so the new OTA installs without errors?
@muniz_ri thank you sir you're certainly a credit to this community
muniz_ri said:
G900A_NG3_tA1_OTA.zip
Click to expand...
Click to collapse
Just a warning to others, this OTA caused my wife's S5 to have the data partition erased. That really ticked her off, she still pissed cause it lose a lot of her data. I thought it was like an ordinary OTA and didn't erase data. I dropped it on the SD card, didn't backup any of her internal storage data, and booted into recovery and applied the update via external storage. It ran for about 15mins and one of the last lines on the screen said "Formatting /data....." Not sure why it did that. Didn't see it anywhere in the update-script inside.
I should've learned my lesson from another S3 experience like that a year or so ago, caused the phone to somehow lose all data, should backed up everything ahead of time.
Dixit
dixit said:
Just a warning to others, this OTA caused my wife's S5 to have the data partition erased. That really ticked her off, she still pissed cause it lose a lot of her data. I thought it was like an ordinary OTA and didn't erase data. I dropped it on the SD card, didn't backup any of her internal storage data, and booted into recovery and applied the update via external storage. It ran for about 15mins and one of the last lines on the screen said "Formatting /data....." Not sure why it did that. Didn't see it anywhere in the update-script inside.
I should've learned my lesson from another S3 experience like that a year or so ago, caused the phone to somehow lose all data, should backed up everything ahead of time.
Dixit
Click to expand...
Click to collapse
This happen if you load from SD-CARDS. If you push true ADB sideload will not erase data.
Clicking from notecable N910A
norbarb said:
This happen if you load from SD-CARDS. If you push true ADB sideload will not erase data.
Clicking from notecable N910A
Click to expand...
Click to collapse
Damn. I had no clue. Now I know. That explains why a few times on adb sideload is never did it. Thanks for the clarification.
Dixit
muniz_ri said:
**Make certain that your reactivation lock in security settings is off before beginning this process**
1. Take the OA1 OTA update.
2. Download and install Towelroot-v3.apk(this version does not require internet access).
3. Place your phone into "Download Mode" (press and hold the Home, Volume Down, and Power keys until the phone powers on and displays warning screen, then press Volume Up key) and flash the G900A_ND3_Stock_Kernel using Odin's PDA slot(AP in Odin v3.09+).
4. Open the Towelroot app from your app drawer and press "Make it Rain" to root your device.
5. Power off then boot into "Download Mode" again and flash the G900A_OA1_Stock_Kernel also using Odin's PDA slot(AP in Odin v3.09+).
6. Install SuperSU to manage root access. Done!
Changelog: http://www.att.com/esupport/article.jsp?sid=KB424848&cv=820&_requestid=1642069
Notes:
1. After flashing the ND3 kernel your phone will run a little wonky and towelroot may not root on the first try. If that happens reboot and try towelroot once again. Once rooted and after flashing the OA1 kernel your phone will once again run like a champ!
2. Following the above process will not affect your User Data or Knox Warranty Flag.
3. Should the OA1 ota update fail consider returning to stock NCE by flashing the G900A_Downgrade_to_NCE.tar using Odin's PDA slot(AP in Odin v3.09+) then taking the OA1 OTA update. Once updated to OA1 continue from Step 2 above.
Alternative Method for Safestrap Users:
1. Place the G900A_OA1_100%_Stock_Rooted_ROM.zip onto your ext-sdcard.
2. Use Safestrap's Backup Function to back-up User Data.
3. From the Safestrap recovery perform an "Advanced Wipe" and wipe everything but your ext-sdcard.
4. Flash the G900A_OA1_100%_Stock_Rooted_ROM.zip using Safestrap's "Stock Slot."
5. Then press "Home" then "Restore" and restore User Data.
6. Once complete press "Home" then "Reboot" and reboot into "Download" mode.
7. Last, flash the G900A_OA1_Stock_Kernel using Odin's PDA slot(AP in Odin v3.09+).
Notes:
1. The above process will update your Modem, Non-hlos, System, Kernel, Stock Recovery, and Bootloader to OA1.
Click to expand...
Click to collapse
Should I wait until android lollipop to come out to root or should I just go ahead and root now?
So like... I got status code 7... And obviously the first thing everyone will say is search xD So I did, and I found the reason being is because, self-explanitory like the log says, it has to do with secEmail_K.apk... Well I uninstalled it with tibu.. Thing is, I had a backup of it, but what I hadn't realized is that was a backup from NCE instead of NG3... I didn't think it would make a difference as I thought "Well the app is the app right?" Well nope... And from what I can understand, it would be illegal for someone to just hand that over to me. Is there any way without factory reset to get this? Thank you in advance.
kenslee123 said:
Should I wait until android lollipop to come out to root or should I just go ahead and root now?
Click to expand...
Click to collapse
We may not even see a rooted lollipop (stock kernel and bootloader) so enjoy root on kitkat
SkyAttacksX said:
So like... I got status code 7... And obviously the first thing everyone will say is search xD So I did, and I found the reason being is because, self-explanitory like the log says, it has to do with secEmail_K.apk... Well I uninstalled it with tibu.. Thing is, I had a backup of it, but what I hadn't realized is that was a backup from NCE instead of NG3... I didn't think it would make a difference as I thought "Well the app is the app right?" Well nope... And from what I can understand, it would be illegal for someone to just hand that over to me. Is there any way without factory reset to get this? Thank you in advance.
Click to expand...
Click to collapse
The only way now is use the method to go back to NCE that Muniz has provided then take the NG3 and then OA1 update OTA. You will lose all internal data so back it up.
Muniz... I had used your instructions in another thread to go from a rooted ND3 to NG3 (after having to do the NCE downgrade) and all is well.
Because I use some apps that require an unrooted device, I used SuperSU's feature to unroot. All well up to this point.
Now the OA1 OTA update fails. I tried it as well with and adb sideload, and get an error indicating that /system/etc/permissions/platform.xml has incorrect data. I had modified it to allow RW access to the External SD card.
Question: without having to go trough the ordeal of downgrading to NCE, could I just Odin ND3 Kernell, root, update the platform.xml file, Odin back to NG3 Kernel, unroot and get the OA1 OTA, and then possibly Odin back to ND3 Kernel to root again, modify the platform.xml for Ext-SD permissions, Odin to OA1 Kernel, unroot, or some sort of combination of abover? I' just am too lazy to go to NC3 which wipes all out and then having to redo all my settings/apps....... Thanks
akitten007 said:
We may not even see a rooted lollipop (stock kernel and bootloader) so enjoy root on kitkat
Click to expand...
Click to collapse
From the Verizon forums for their Lollipop version. Safestrap upgrade for a rooted Lollipop rom. Muniz is a wizard and so far with every release it appears what happens with Verizon Roms is what can be done with ATT Roms. http://forum.xda-developers.com/showthread.php?p=58608519
CAG-man said:
From the Verizon forums for their Lollipop version. Safestrap upgrade for a rooted Lollipop rom. Muniz is a wizard and so far with every release it appears what happens with Verizon Roms is what can be done with ATT Roms. http://forum.xda-developers.com/showthread.php?p=58608519
Click to expand...
Click to collapse
Are we sure this method works for AT&T S5 rooted and using safestrap??
If I have already gotten to 4.4.4 through OTA updates can I simply run towelroot against the currently installed OTA OA1 Rom?
cor_su said:
If I have already gotten to 4.4.4 through OTA updates can I simply run towelroot against the currently installed OTA OA1 Rom?
Click to expand...
Click to collapse
Please read the op
SM-G870A Peace
---------- Post added at 10:55 AM ---------- Previous post was at 10:54 AM ----------
3volved said:
Are we sure this method works for AT&T S5 rooted and using safestrap??
Click to expand...
Click to collapse
We can't be sure until we get lollipop on our devices.
SM-G870A Peace
My note 3 was rooted on oc1 for a few months, then about a month ago it started randomly rebooting during the day. Sometimes it would boot normally, other times it would bootloop until i cleared the cache multiple times. I then went into safestrap to clear the cache and dalvik, and that ended the random restarts for about a week until it started happening again. To make sure it wasnt the sd card, i swapped sd cards and even removed it entirely, still was getting random bootloops. I got rid of the root and reverted to 100% stock oc1 using the 4 odin tars, then i upgraded to oc2 stock. Still, i am getting bootloops even on a stock rom. What are my options?
Were you getting bootloops on OC1?
IAnb3rlin said:
Were you getting bootloops on OC1?
Click to expand...
Click to collapse
Yes, my oc1 was rooted and i was getting bootloops. Now that i reverted to stock oc1, and upgraded to oc2 using OTA, i am still getting random restarts and bootloops.
Could you post an "about device" screen shot that includes version, baseband, kernal, build, and security
IAnb3rlin said:
Could you post an "about device" screen shot that includes version, baseband, kernal, build, and security
Click to expand...
Click to collapse
There we go, i put 2 pics in the attachments
Zenoah said:
There we go, i put 2 pics in the attachments
Click to expand...
Click to collapse
Awesome. Could you also link me to the files your putting inside odin? Have you checked the files md5 to make sure they're correct?
To get to 5.0 OC1 originally, did you downgrade to 4.2 NC2 then root with towelroot, install supersu, busybox, safestrap, then flash rooted OC1?
IAnb3rlin said:
Awesome. Could you also link me to the files your putting inside odin? Have you checked the files md5 to make sure they're correct?
To get to 5.0 OC1 originally, did you downgrade to 4.2 NC2 then root with towelroot, install supersu, busybox, safestrap, then flash rooted OC1?
Click to expand...
Click to collapse
i used the individual wipe tars from this thread http://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609
When i rooted i did downgrade to nc2, did towelroot, supersu, busybox, and safestrap then flashed to oc1 rooted.
Give this a try:
* Make sure to check the MD5s to ensure they downloaded intact. I use http://www.winmd5.com/
1. Downgrade to 4.4.2, using the Full Odin Tar., then root with towelroot, install busybox, safestrap, supersu.
2. https://www.androidfilehost.com/?fid=95784891001615211 (N900AUCUCNC2_Full_Odin_Tar)
* Make sure you place this in the odin PDA or AP slot. (depending on which version you have)
3. Now, once your on 4.4.2 rooted, flash this https://www.androidfilehost.com/?fid=95916177934549604 (SM-N900A_OC1_Lollipop_Rooted_Rom.zip) by booting into Safestrap, factory resetting, and then finally flashing.
4. The AT&T logo will sit there for what feels like forever. This is normal.
5. Let me know if this works.