Related
Hi Guys,
Am an avid xda fan. Been using Androids since the Nexus One and am on my 4th phone, the Z1 now. Im quite comfortable with modding phones , unlocking boot loaders etc however am in a situation.
I have got an Unlocked Z1 (obtained from Telstra, Australia) and have successfully got root. I followed the steps for Kingo and have verified SU status. Now heres my problem, I restored a bunch of system backups from Titanium backup from my old phone (Samsung S4). The S4 had CM10.2 on it before. After installing a select few system backups and the suggested reboot, i now get boot loops. It boots up to the Sony logo and splash screen however as soon as i see 1-2 seconds of my home screen, it reboots. and it loops. I need help guys as I don't have a custom recovery installed to do wipe phone in recovery.
Problem: Bootloop after Titanium backup restore
Situation: have Root (SU), bootloader locked, no custom Recovery.
Any suggestions? Am open for anything. Thanks guys.
mokuni said:
Hi Guys,
Am an avid xda fan. Been using Androids since the Nexus One and am on my 4th phone, the Z1 now. Im quite comfortable with modding phones , unlocking boot loaders etc however am in a situation.
I have got an Unlocked Z1 (obtained from Telstra, Australia) and have successfully got root. I followed the steps for Kingo and have verified SU status. Now heres my problem, I restored a bunch of system backups from Titanium backup from my old phone (Samsung S4). The S4 had CM10.2 on it before. After installing a select few system backups and the suggested reboot, i now get boot loops. It boots up to the Sony logo and splash screen however as soon as i see 1-2 seconds of my home screen, it reboots. and it loops. I need help guys as I don't have a custom recovery installed to do wipe phone in recovery.
Problem: Bootloop after Titanium backup restore
Situation: have Root (SU), bootloader locked, no custom Recovery.
Any suggestions? Am open for anything. Thanks guys.
Click to expand...
Click to collapse
hi mate, of course it will be boot loop. you restore system backup to your z1, it wont work. you need to reset your handheld to factory again.
next time please don't restore your system backup (use XML backup for backup call, wireless access point, phone log, message), just user data backup, such as apps you are using.
antec123 said:
hi mate, of course it will be boot loop. you restore system backup to your z1, it wont work. you need to reset your handheld to factory again.
next time please don't restore your system backup (use XML backup for backup call, wireless access point, phone log, message), just user data backup, such as apps you are using.
Click to expand...
Click to collapse
Hey bro. can you explain how I cna reset it back to factory again? without booting the phone?
yea, in hind sight i should have, plus was playing with fire, especially having no custom recovery.
edit: im thinking probably having to use adb/fastboot/flashtool of some sort. Just trying to figure out the commands...
mokuni said:
Hey bro. can you explain how I cna reset it back to factory again? without booting the phone?
yea, in hind sight i should have, plus was playing with fire, especially having no custom recovery.
edit: im thinking probably having to use adb/fastboot/flashtool of some sort. Just trying to figure out the commands...
Click to expand...
Click to collapse
You need to flash a ftf firmware file using Flash Tool (similar to flashing a stock ROM in Odin with Samsung). There are guides for doing it out there on this forum as well as ftf downloads. It will take you back to pure stock.
Sent from my C6902 using Tapatalk
301stSpartan said:
You need to flash a ftf firmware file using Flash Tool (similar to flashing a stock ROM in Odin with Samsung). There are guides for doing it out there on this forum as well as ftf downloads. It will take you back to pure stock.
Sent from my C6902 using Tapatalk
Click to expand...
Click to collapse
yup figured as much. downloading a generic tft file for the z1 as we speak. Thanks for confirming my thoughts. will update once Ive resolved this issue.
Mok
mokuni said:
yup figured as much. downloading a generic tft file for the z1 as we speak. Thanks for confirming my thoughts. will update once Ive resolved this issue.
Mok
Click to expand...
Click to collapse
sorry mate, i don't have z1 but the procedure of backup & restore is like that you cannot restore your previous system with different model. btw good luck with resetting your device.
mokuni said:
yup figured as much. downloading a generic tft file for the z1 as we speak. Thanks for confirming my thoughts. will update once Ive resolved this issue.
Mok
Click to expand...
Click to collapse
Yup that fixed it. Thnks guys for the confirmation. the restore of a generic tft file with flashtool not only resolved my issue, but also as expected wiped any carrier customisation i.e. Telstra.
I have a Moto X developer edition and I've been trying to OTA update to 139.15.1 but my phone fails with the error code 410. I found the Flashable zip and so I'm going to install it with that but for future installs how do I do it with the OTA. The phone failed both while rooted and while running a stock nandroid I made before rooting. With the stock nandroid the only thing modified was the unlocked bootloader. Yes I am using the stock recovery. Any help would be greatly appreciated.
Scoopta said:
I have a Moto X developer edition and I've been trying to OTA update to 139.15.1 but my phone fails with the error code 410. I found the Flashable zip and so I'm going to install it with that but for future installs how do I do it with the OTA. The phone failed both while rooted and while running a stock nandroid I made before rooting. With the stock nandroid the only thing modified was the unlocked bootloader. Yes I am using the stock recovery. Any help would be greatly appreciated.
Click to expand...
Click to collapse
there are threads out there already describing how to take the ota on a dev phone. But pure curiosity here, how in the hell are you making nandroid backups with stock recovery? I had noidea stock recovery allowed you to make those backups. I thought that was the point of other recoveries.
jayboyyyy said:
there are threads out there already describing how to take the ota on a dev phone. But pure curiosity here, how in the hell are you making nandroid backups with stock recovery? I had noidea stock recovery allowed you to make those backups. I thought that was the point of other recoveries.
Click to expand...
Click to collapse
It isn't possible to make a nandroid backup with a stock recovery. I meant I reflashed the stock recovery after making the backup. Anyway it is possible to make a backup that includes your stock recovery by using the fastboot boot command to boot to a recovery over usb rather than flashing it to your recovery partition.
Scoopta said:
It isn't possible to make a nandroid backup with a stock recovery. I meant I reflashed the stock recovery after making the backup. Anyway it is possible to make a backup that includes your stock recovery by using the fastboot boot command to boot to a recovery over usb rather than flashing it to your recovery partition.
Click to expand...
Click to collapse
interesting. Still wouldn't expect the OTA to work if you booted that way though. The OTA would be checking the files on the phone not the files from the usb that are running the phone. I wouldn't think. But I could be really confused on what you just said. Either way, there are several threads on the matter that should adequately answer all your needs.
jayboyyyy said:
interesting. Still wouldn't expect the OTA to work if you booted that way though. The OTA would be checking the files on the phone not the files from the usb that are running the phone. I wouldn't think. But I could be really confused on what you just said. Either way, there are several threads on the matter that should adequately answer all your needs.
Click to expand...
Click to collapse
Yes it would appear you are confused on what I just said. Anyway I guess I'll browse around to find instructions on how to take an OTA for the next time there's an OTA released.
Scoopta said:
Yes it would appear you are confused on what I just said. Anyway I guess I'll browse around to find instructions on how to take an OTA for the next time there's an OTA released.
Click to expand...
Click to collapse
i get what you were saying now. I thought you were saying that you were booting your phone from a usb drive that had the stock recovery on it so you could see if the OTA would take on your phone. Anyway, I dont' remember all of the steps that people were taking but it was pretty simplistic.
jayboyyyy said:
i get what you were saying now. I thought you were saying that you were booting your phone from a usb drive that had the stock recovery on it so you could see if the OTA would take on your phone. Anyway, I dont' remember all of the steps that people were taking but it was pretty simplistic.
Click to expand...
Click to collapse
ok...thanks for the info. I'll see if I can find a thread on it.
Hey all, I have searched and searched but can't seem to find anything. Tried removing carrier iq the wrong way, just removed the files from the system, caused a boot loop, I'm rooted but don't have a custom recovery installed, can someone direct me to the correct file to flash by Odin to install a custom recovery? That way I can reinstall / move the files back to where they were? Will this work? Thanks a lot! Jeremy
There is no custom recovery for the AT&T Note 3. You said you're on 4.4.2, correct? If so, you'll have to use the MLG restore (see the link in my signature for a guide) or go to a Samsung Experience Center at your local Best Buy and have them reflash your phone.
Thanks, that's what I was thinking. And as far as best buy, I've tried before and the guy there said flashing a rooted phone will brick it and he absolutely would not do it so... And that's the only best buy around so...
jeremyds45 said:
Thanks, that's what I was thinking. And as far as best buy, I've tried before and the guy there said flashing a rooted phone will brick it and he absolutely would not do it so... And that's the only best buy around so...
Click to expand...
Click to collapse
I took my rooted phone to Best Buy when it was on MJ5 in order to update to OTA 4.4 when it was released, and it worked just fine. Maybe something changed then.
jeremyds45 said:
Thanks, that's what I was thinking. And as far as best buy, I've tried before and the guy there said flashing a rooted phone will brick it and he absolutely would not do it so... And that's the only best buy around so...
Click to expand...
Click to collapse
That guy is full of ****.
SpikeyPsyche said:
That guy is full of ****.
Click to expand...
Click to collapse
Yeah what I was thinking, he doesn't know what he's talking about pretty much, I didn't want to even go up there and try because of the lack of knowledge. But now I do want to flash my phone to nc2 stock and go from there. Are we sure that I can? I'm running the flashed method of the mj5 itself, no nc2 kernel or anything, just the flashed mj5 from Carl's post.
jeremyds45 said:
Yeah what I was thinking, he doesn't know what he's talking about pretty much, I didn't want to even go up there and try because of the lack of knowledge. But now I do want to flash my phone to nc2 stock and go from there. Are we sure that I can? I'm running the flashed method of the mj5 itself, no nc2 kernel or anything, just the flashed mj5 from Carl's post.
Click to expand...
Click to collapse
thats MGL with A3 bootloader, if you install that then you will not have any trace of Root. You can do a factory reset first and then install that odin install, then go to AT&T if thats your carrier and they may do more for you than best buy.
Or do this if you want official nc2 4.4.2 http://forum.xda-developers.com/showthread.php?t=2701062
jerrycoffman45 said:
Or do this if you want official nc2 4.4.2 http://forum.xda-developers.com/showthread.php?t=2701062
Click to expand...
Click to collapse
thats only good if you have the A2 older bootloader, I think jeremyds45 took the A3 bootloader, to my understanding
That's what he has he said he flashed mj5
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
Now if he has mlg I would suggest he use your nc2 thread in development
If anyone is interested in the future, best buy can indeed flash the official NC2 4.4.2 kitkat to your note 3 as long as you're not on verizon, rooted, or have tripped knox, have a custom rom or the like. When i went in this time i actually spoke to someone who knew something and hooked me up, samsung rep, plugged it in to their computer, downloaded the software, rebooted and all was back to normal. Just like an official ota update, didn't lose any of my files, settings anything. So we're back, and now rooted and rollin.
So basically anyone who installed safestrap and doesn't have a working backup is out of luck.
440bro said:
So basically anyone who installed safestrap and doesn't have a working backup is out of luck.
Click to expand...
Click to collapse
If you want to go back to stock 4.4.2, you can flash by odin the leaked tar, which will remove root, and everything, then go to best buy have them flash the nc2 official, then start from scratch there, with rooting and safestrap etc.
440bro said:
So basically anyone who installed safestrap and doesn't have a working backup is out of luck.
Click to expand...
Click to collapse
Can't you just uninstall safestrap and delete any root files off the internal SD card?
Sent from my SM-N900A using XDA Free mobile app
Hi, I followed the guide to install CWM and it seemed to go fine, but when I power on the phone and tap the vol-down key nothing happens, I do get the vibrations as I'm doing it though. Is CWM really necessary to install a custom rom? Cos I might just skip it.
You can't flash a custom rom without cwm recovery.
Sent from my C2104 using XDA Free mobile app
karthikys1 said:
You can't flash a custom rom without cwm recovery.
Sent from my C2104 using XDA Free mobile app
Click to expand...
Click to collapse
O lol, I guess I need to solve this then. I thought I just used FlashTool to flash the rom and viola, rom is on.
Does anyone have any ideas what I might be able to try to figure out why CWM isn't working? Any way to see if CWM is actually on my phone? (Maybe it's just not there, rather then not working).
Edit: Rom Manager seems to think I have CWM installed, also I did a Nandroid Backup which seemed to be configured to use CWM so I don't know if it's there or not, or working or not
Which guide did you follow? And how did you make a Nandroid Backup?
I followed this guide.
I downloaded Nandroid Backup Root, it created the backup without rebooting the phone, so it never needed to boot into CWM.
Astralogic said:
I followed this guide.
I downloaded Nandroid Backup Root, it created the backup without rebooting the phone, so it never needed to boot into CWM.
Click to expand...
Click to collapse
That's what I thought. The fact that it can create a backup doesn't mean it has a recovery installed, it doesn't use a recovery to create it. If the LED is lighting up at boot, and it is vibrating, and it doesn't get back in, I don't know what the problem would be. I'd try reinstalling CWM, and FYI, you should use V8; V9 has issues.
At the very least, if it really is installed, you should have a "recovery.tar" and "chargemon" file in /system/bin/.
Antiga Prime said:
That's what I thought. The fact that it can create a backup doesn't mean it has a recovery installed, it doesn't use a recovery to create it. If the LED is lighting up at boot, and it is vibrating, and it doesn't get back in, I don't know what the problem would be. I'd try reinstalling CWM, and FYI, you should use V8; V9 has issues.
At the very least, if it really is installed, you should have a "recovery.tar" and "chargemon" file in /system/bin/.
Click to expand...
Click to collapse
I don't have those files so CWM is not installed. I can't find v8 of CWM for Xperia T but I found this file "CWM4XperiaT_v8i_JB.zip", is that it?
Astralogic said:
I don't have those files so CWM is not installed. I can't find v8 of CWM for Xperia T but I found this file "CWM4XperiaT_v8i_JB.zip", is that it?
Click to expand...
Click to collapse
It clearly says "Xperia T" in the name of that file... yes, that's it. Now I'm wondering what you installed, if you didn't install that one, or V9.
Antiga Prime said:
It clearly says "Xperia T" in the name of that file... yes, that's it. Now I'm wondering what you installed, if you didn't install that one, or V9.
Click to expand...
Click to collapse
V8 works perfectly, it's installed fine.
I am going to follow this guide to install cyanogenmod, do I need to obtain a bootloader unlock code? Or should I just skip right to installing the ROM?
Edit: Oops forgot the link: http://wiki.cyanogenmod.org/w/Install_CM_for_mint
Astralogic said:
V8 works perfectly, it's installed fine.
I am going to follow this guide to install cyanogenmod, do I need to obtain a bootloader unlock code? Or should I just skip right to installing the ROM?
Edit: Oops forgot the link: http://wiki.cyanogenmod.org/w/Install_CM_for_mint
Click to expand...
Click to collapse
First of all, yes, you need an unlocked bootloader. You can't flash custom kernels on a locked bootloader. Secondly, I've never tried that tutorial (I have a TX), but I'm assuming it should work fine, but, personally I'd either go with FXP, or one of the OMNI builds here in XDA, since, as far as I know, developers here have more fixes than what I've seen on FXP and/or CM.
Also, there are a easier ways to flash your ROM, since you already have a custom ROM. I don't think it's necessary to have to fastboot the kernel first.
Edit: The Carbon ROM I'm on also has a T version. The reason I'm on this ROM (and previously OMNI) was because FXP/CM roms have/had a battery drain that was never fixed, something that was fixed here on XDA.
Antiga Prime said:
First of all, yes, you need an unlocked bootloader. You can't flash custom kernels on a locked bootloader. Secondly, I've never tried that tutorial (I have a TX), but I'm assuming it should work fine, but, personally I'd either go with FXP, or one of the OMNI builds here in XDA, since, as far as I know, developers here have more fixes than what I've seen on FXP and/or CM.
Also, there are a easier ways to flash your ROM, since you already have a custom ROM. I don't think it's necessary to have to fastboot the kernel first.
Edit: The Carbon ROM I'm on also has a T version. The reason I'm on this ROM (and previously OMNI) was because FXP/CM roms have/had a battery drain that was never fixed, something that was fixed here on XDA.
Click to expand...
Click to collapse
There's a problem My bootloader is not unlockable... does this mean I've been wasting my time?
Edit: There is this guide, it makes no mention of unlocking the bootloader so it might work?
Astralogic said:
There's a problem My bootloader is not unlockable... does this mean I've been wasting my time?
Edit: There is this guide, it makes no mention of unlocking the bootloader so it might work?
Click to expand...
Click to collapse
No, that tutorial won't work. Never follow a guide for flashing ROMs that wasn't meant for your phone. Your phone didn't even exist yet when that guide was written.
If you can't unlock your bootloader then there is no way you'll ever be able to flash a custom ROM, because, like I mentioned earlier, custom ROMs have custom kernels, and custom kernels need an unlocked bootloader.
I wouldn't consider it a waste, it's always useful to have a recovery installed; with it you can at the very least backup and restore, flash deodexed/zipaligned stock ROMs, such as this one, flash files, and even have access to ADB if your phone doesn't boot up, which can save you from having to wipe everything, etc., so not a complete waste of time.
Antiga Prime said:
No, that tutorial won't work. Never follow a guide for flashing ROMs that wasn't meant for your phone. Your phone didn't even exist yet when that guide was written.
If you can't unlock your bootloader then there is no way you'll ever be able to flash a custom ROM, because, like I mentioned earlier, custom ROMs have custom kernels, and custom kernels need an unlocked bootloader.
I wouldn't consider it a waste, it's always useful to have a recovery installed; with it you can at the very least backup and restore, flash deodexed/zipaligned stock ROMs, such as this one, flash files, and even have access to ADB if your phone doesn't boot up, which can save you from having to wipe everything, etc., so not a complete waste of time.
Click to expand...
Click to collapse
Ok, well, I learned a bit in the process, and I still have an Xperia SP bootloader to unlock, then flash cyanogenmod, so I'm in a better position to handle that now, thanks for all the help guys.
I rooted vs98039a with a one click root method on xda. Everything worked perfect! The only thing is, I don't have a recovery. When I try to boot into recovery, I get android on his back with the red triangle . Anyone know how to install twrp? I can't even do a backup. How do I do a nandroid backup? It's been a long time since I've done this and can't remember.
jimecv88 said:
I rooted vs98039a with a one click root method on xda. Everything worked perfect! The only thing is, I don't have a recovery. When I try to boot into recovery, I get android on his back with the red triangle . Anyone know how to install twrp? I can't even do a backup. How do I do a nandroid backup? It's been a long time since I've done this and can't remember.
Click to expand...
Click to collapse
You can use autorec for kk and the new autorec for lp please as sugested use tge search feature to locate the proper threads.
tsjanda said:
You can use autorec for kk and the new autorec for lp please as sugested use tge search feature to locate the proper threads.
Click to expand...
Click to collapse
Onto your question...
What oneclick method? Do you have a link? Some install a recovery, some are simply root. If you're coming from 39a stock, you need to use XDABEBB's 39a bootstack (get it here) (keeps the 39a modem, rolls back to an older bootloader as Bump is patched in 39a so you can't boot anything but stock. Your oneclick method likely flashed a recovery, but not a bootstack.... Which is what's causing the dead android when you boot recovery. You're really lucky it didn't flash everything though as you could've possibly bricked your phone if it had.
You should have used Freedom Tool which would have got you what you needed... or maybe the new autorec.
Read Twice, Flash once.
Super sorry about the wrong forum. I thought I was at right place. How can I move this post to the right place? Again, sorry to bother you guys. You do great work!!!
jimecv88 said:
Super sorry about the wrong forum. I thought I was at right place. How can I move this post to the right place? Again, sorry to bother you guys. You do great work!!!
Click to expand...
Click to collapse
No need, I flagged the post so the moderators would move it. They also cleaned up the thread.
Even if you're already rooted you can run that tool I linked, it will fix what was messed up.
The freedom tool, or the bootstack?
jimecv88 said:
The freedom tool, or the bootstack?
Click to expand...
Click to collapse
He means the freedom tool, the bootstack is a file you would flash in twrp.