Database Users

[Q] One Click vs Unlocked Bootloader

Simple question, one i didn't find a quick simple answer too.
I know the main differences between one-click root and unlocking the bootloader, and the biggest for me was the warranty. I used one-click root so just in case, I could revert back. Now my warranty is just about up, and I figure why not? My biggest question is, will it provide any benefits?
For some reason I have never been able to install themes (either update.zip files or through metamorph), I just go into an infinite boot loop. I was hoping this was the only issue. But I don't know enough to know the answer

Benefits are safer radio flashing, and if you ever **** the phone up so bad you can't boot into anything other than the bootloader, you can fastboot flash everything required to get going again.

Rusty! said:
Benefits are safer radio flashing, and if you ever **** the phone up so bad you can't boot into anything other than the bootloader, you can fastboot flash everything required to get going again.
Click to expand...
Click to collapse
One more little question; Should i reflash CM7 (im running the nightlies currently) when its done? I read that it will wipe all data (already got everything backed up ready to go) but I was just wondering if I would need to reflash anything right now, like CM7 or the recovery?

Take NANDroid, unlock, restore NANDroid, continue as if nothing happened.

Rusty! said:
Take NANDroid, unlock, restore NANDroid, continue as if nothing happened.
Click to expand...
Click to collapse
Tons of awesomesauce I guess thats what I will go ahead and do! Thank you so very much for the quick help!
EDIT: Done, restoring the NANDroid backup now I hesitated a little bit when hitting that button though, a year of me holding back doing it because of the warranty was still making my trigger finger nervous
... And back in my rom, everything normal once again And again thanks for the quick help.

Well not so normal; I have lost my setup accounts, and everytime I try restoring a NANDroid the accounts are still gone, and there isn't an option to add in a google account and none of the google apps work. No force closes just closes the second you try to open it.
I have tried reflashing both the rom and gapps, still no good.
Am i going to need to wipe?

Certainly shouldn't do, I unlocked my bootloader in the same way and everything continued as normal.
Bit odd that you can't add your account back though, the option should be there under accounts & sync.
It sounds like what happens when you try and use CM without adding GApps

That's what I thought too. So I tried flashing gapps, nothing.
Went ahead and did a full wipe. Quite amazed so far what all android is restoring for me. Nearly all back
Sent from my Nexus One using XDA App

Bootloader Loop problem

Hi, my phone acted weird today, been running custom room for over couple months without any problem, but then when i resart my phone today it got to the bootload screen and stuck there ever seen. I can able to go into custom recover and did a full wipe but nothing change, could anyone help me out? I have loki also. Using S4 ATT version.

Try wiping cache in your recovery

i did that, always do that after install a new rom, don't know why my phone is soft bricked now...

akahimaro said:
i did that, always do that after install a new rom, don't know why my phone is soft bricked now...
Click to expand...
Click to collapse
if you've done a full wipe and tried either re-flashing your rom or restoring a nandroid and neither was successful, you may need to consider going back to stock via odin and starting over.
i've never seen a phone run on the same rom and kernel settings for months and then just shut down and softbrick without something having been changed recently.

xBeerdroiDx said:
if you've done a full wipe and tried either re-flashing your rom or restoring a nandroid and neither was successful, you may need to consider going back to stock via odin and starting over.
i've never seen a phone run on the same rom and kernel settings for months and then just shut down and softbrick without something having been changed recently.
Click to expand...
Click to collapse
yes, i'm doing that right now, thanks for the tips, i had that happen to my s2 before. Really weird...

Before ODIN'ing back to MDL/MDB...
akahimaro said:
yes, i'm doing that right now, thanks for the tips, i had that happen to my s2 before. Really weird...
Click to expand...
Click to collapse
What recovery image are you running? You are not the only one that had this problem. I am trying to piece this together.

Phone keeps bootlooping, possible EFS corruption?

I tried flashing X-Note 6.0 and things have gone sour from there. I keep getting bootloop, i'm able to do initial setup until it asks me for gmail, once i input my address, it pulls my name and when it asks me to confirm it, it restarts the phone. Then im able to finish setup, but as soon as i'm back and i reboot again, im stuck in infinite bootloop.
I tried reverting back to stock via odin, but i got bootloop again, fortunately for me, after about 1h, it booted back into OS and i was able to root and reinstall twrp.
I dont have a backup of my EFS, again i'm not even sure thats the real problem, can anybody please help?
EDIT: On stock the bootloop is not infinite, after about 10 minutes the phone eventually boot back in OS

polish_pat said:
I tried flashing X-Note 6.0 and things have gone sour from there. I keep getting bootloop, i'm able to do initial setup until it asks me for gmail, once i input my address, it pulls my name and when it asks me to confirm it, it restarts the phone. Then im able to finish setup, but as soon as i'm back and i reboot again, im stuck in infinite bootloop.
I tried reverting back to stock via odin, but i got bootloop again, fortunately for me, after about 1h, it booted back into OS and i was able to root and reinstall twrp.
I dont have a backup of my EFS, again i'm not even sure thats the real problem, can anybody please help?
EDIT: On stock the bootloop is not infinite, after about 10 minutes the phone eventually boot back in OS
Click to expand...
Click to collapse
Please help me someone. I tried the EFS fix here with no success. I tried to restore via odin, factory reset, every time i finish initial setup and restore my apps and reboot, it bootloops.

Shot in the dark, but disable auto installing of apps/restoring apps. Could be that it is triggering the bootloop due to an incompatible app with X-Note.
If no good. You gotta be brave and strip that badboy back with a full wipe/dalvik/cache, reflash your stock image (get shot of recovery also) then see if it can get past the bootloop (don't forget to remove your SD Card also if you have one) - Give it shot, see what you come up with.
Also if you're on an N9005 model, head over to Djembays thread and grab an image of him, seems to have gotten a lot of people out of issues (JayTheNut uses his images when he messes up) -
Lemme know how you get on, I'll have a nose around see what else it could be.

radicalisto said:
Shot in the dark, but disable auto installing of apps/restoring apps. Could be that it is triggering the bootloop due to an incompatible app with X-Note.
If no good. You gotta be brave and strip that badboy back with a full wipe/dalvik/cache, reflash your stock image (get shot of recovery also) then see if it can get past the bootloop (don't forget to remove your SD Card also if you have one) - Give it shot, see what you come up with.
Also if you're on an N9005 model, head over to Djembays thread and grab an image of him, seems to have gotten a lot of people out of issues (JayTheNut uses his images when he messes up) -
Lemme know how you get on, I'll have a nose around see what else it could be.
Click to expand...
Click to collapse
I dont think you read the thread. I'm not on xnote anymore, i'm on stock firmware, MJ4, i also have a W8 and the EFS script fix is for international version. I've odined back to stock and all the issues i'm having are also present on stock firmware

polish_pat said:
I'm not on xnote, i'm on stock firmware, MJ4, i also have a W8 and the EFS script fix is for international version
Click to expand...
Click to collapse
Ah ok, so that changes the playing field a little. - Give @CalcProgrammer1 a Message, he uses the W8 and the guy certainly knows a thing or two about it. All I can think of at this time.
EDIT: actually thinking about it, you haven't upgraded your bootloader by mistake have you?

I have a feeling background WiFi scanning is enabled in Settings -> WiFi -> Advanced - I don't think any of the newer ROM updates ever managed to have that not bootloop your phone on reboot. In case you're stumped and can't find the setting, you'll have to hit the menu key on the WiFI screen.

radicalisto said:
Ah ok, so that changes the playing field a little. - Give @CalcProgrammer1 a Message, he uses the W8 and the guy certainly knows a thing or two about it. All I can think of at this time.
EDIT: actually thinking about it, you haven't upgraded your bootloader by mistake have you?
Click to expand...
Click to collapse
I dont think so, unless flashing Xnote 6.0 or using odin to restore stock does that. Thats pretty much all I did, but i think i might have done something that might have fixed the problem, i'm not sure yet, but i'll confirm shortly

radicalisto said:
Ah ok, so that changes the playing field a little. - Give @CalcProgrammer1 a Message, he uses the W8 and the guy certainly knows a thing or two about it. All I can think of at this time.
EDIT: actually thinking about it, you haven't upgraded your bootloader by mistake have you?
Click to expand...
Click to collapse
I use the N900T (T-Mo) version, though I guess it's pretty similar to the W8. Unfortunately I don't know anything about the efs side of things on the N900T or equivalents. I've been avoiding the backup and restore functionality in TWRP since it was widely reported to cause bootloops in the first few weeks after release anyways. Have you tried the bootloop fix method over at the T-Mobile N900T forum? I forget what the process exactly was but people reported great success using it (including those who intentionally recreated the problem to test the fix). I did have a similar boot loop issue on my Note 1 which was fixed doing a complete Odin restore with a full factory image (bootloader, system, modem, kernel, recovery, etc. - the entire complete factory restore). I don't know if such a package exists for the N900W8 and that's something I wouldn't use the wrong variant's version of.

odin was one of the first thing i tried, as mentionned the problem was on 100% stock device. Now i've tried formating SD cards and i was able stop the bootloops but now instead i get a worse problem when my phone keep giving me force closes and everytime i dismiss one, another one pops back up and its just a FC Loop:crying:

I have an W8...I also had terrible boot loop problems and I can't quite remember the cause, but this is what fixed it.
Obviously I can't stress enough to read this and type this in very carefully, and that if your phone stops working, turns into a robot, explodes, or tries to kill your dog I'm not responsible .
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.
Do a factory reset, reboot system
Can't remember where I got this from, only saved the text not the forum >.<

stucked
Hello guys .... I wanna say first ... that I tryed all options and all efs backups etc etc ... everything works just fine back up my efs . and restore but .. when I try to register my phone on network ends like this :
- only emergency calls
- when try to insert a new sim card my n9005 just reboot when search for network also ... is charging but allways remain at 8-10% no more up .
I tryed all kind of stuff ... made back ups .... and tryed install stock firmware etc ... rooting and did anything ... I will apreciate any kind of help ...I just wanna tell you I am close to deat ... becouse is my wife phone and still does not know I messed up with

polish_pat said:
EDIT: I'm offering a 50$ bounty to anybody that gives me a solution that fixes my phone, paid in full by paypal
I tried flashing X-Note 6.0 and things have gone sour from there. I keep getting bootloop, i'm able to do initial setup until it asks me for gmail, once i input my address, it pulls my name and when it asks me to confirm it, it restarts the phone. Then im able to finish setup, but as soon as i'm back and i reboot again, im stuck in infinite bootloop.
I tried reverting back to stock via odin, but i got bootloop again, fortunately for me, after about 1h, it booted back into OS and i was able to root and reinstall twrp.
I dont have a backup of my EFS, again i'm not even sure thats the real problem, can anybody please help?
EDIT: On stock the bootloop is not infinite, after about 10 minutes the phone eventually boot back in OS
Click to expand...
Click to collapse
Hey dude i think xnote 6 is mk2 based, so what basically is going wrong is that you're trying to downgrade your bootloader. please try flashing an mk2 stock rom ( or an mj7) via odin, that should fix it ..
just my 2 cents

Hi guys i tried everything my phone was in a constant state of bootloop and wouldnt connect to any carrier. Then i came across this thread http://forum.xda-developers.com/showthread.php?t=2567133 and now my phone is working, still wont connect to a carrier but the phone is now stable which is a good thing. Hope this helps some of you :fingers-crossed:

Thanks for all the input, as of now, i was able to stop the boot-looping on stock rom, but I do still have major issues like i cannot install twrp, by goomanger it tell me its done but when i reboot into recovery, i end up in stock recovery. And yes, i'm rooted. Also i cannot format my SD card from the OS, it keep telling me the card is being checked all the time. I also have a lot of other small issues that should not be there on a fresh install. i honestly dont know what screwed up so bad but i will try some of the solutions mentioned above and report back.

To me that sounds like your partitions are all screwed up have you tried flashing using a pit file?
Sent from my SM-N9005 using xda app-developers app

Steeno78 said:
To me that sounds like your partitions are all screwed up have you tried flashing using a pit file?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Never. I'm def not that newbish. I dont know whats happening but everytime i format the phone it gets a little better.
Sent from my SM-N900W8 using Tapatalk

Freezing and other issues. Please help.

Running an Australian N9005.
I was running Temaseks unofficial CM11 build just fine. Got bored and wanted to go back to a more Samsung styled phone.
Decided to flash X-Note. As I'd used it before CM11. It worked fine then.
Attempted to flash X-Note but it wouldn't boot, stuck at initial screen with the Kernel warnings at the top of the screen. Was told it was because I hadn't got the new 4.4 bootloader.
I was told to follow the instructions here: http://forum.xda-developers.com/showpost.php?p=46223545&postcount=2
Which I did.
Using these download links and instructions: http://forum.xda-developers.com/showthread.php?p=49931269
That fixed the boot issue. I suppose I'm not on the 4.4 bootloader.
However when I booted up the stock Polish ROM, the initial Samsung Setup Wizard would crash at the end of the setup and force me back to the start of the setup. Tried ignoring it and just flashing the custom recovery and then XNote. Same issue, the setup wizard in XNote crashes as well.
Someone then told me I should try repartitioning the device using a PIT. I don't know what that is, but it was suggested.
Using this ROM: https://mega.co.nz/#!QVwlVDgJ!QyAxmDMcsIA-56cX_28Ua2aPZLcJATVvdM07LOs0V10
And this PIT: http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Completes successfully.
Same issue............... That being a third separate ROM (official? at that)....
Samsung Setup Wizard crashes...
I even tried flashing XNote and removing the setup wizard just to get past it. That fixes it for about 10 minutes or so. After about 10 minutes of use the phone freezes and I have to hold the power button to force it to restart. If I leave the phone off, it still freezes, as soon as I try to unlock it it freezes and need to force restart.
I really don't know what to do now... Any help guys? I'm trying my best here...
Please, if you need any more information, please ask.

Might not help, but have you wiped your phone clean using custom recovery ( data,cache, dalvik, internal sd ) before flashing xnote or factory reset on recovery when on stock?

Do you have reactivation lock enabled?
Sent from my fingers to your face using my Samsung Galaxy Note 3!

hey_joe said:
Might not help, but have you wiped your phone clean using custom recovery ( data,cache, dalvik, internal sd ) before flashing xnote or factory reset on recovery when on stock?
Click to expand...
Click to collapse
Yes.
nicholaschum said:
Do you have reactivation lock enabled?
Click to expand...
Click to collapse
No.

This has puzzled me, not sure why it's still acting up especially after re-partitioning and flatlining everything.

radicalisto said:
This has puzzled me, not sure why it's still acting up especially after re-partitioning and flatlining everything.
Click to expand...
Click to collapse
Yes indeed. I'm very confused...

So... I don't want to get ahead of myself, but my phone seems to have sorted itself out...
I decided to just send it back to the carrier to get it replaced. So I decided to just flash the official Firmware again. (I accidentally left repartition ticked)
Once it started I thought... Oh ****... But I was sending it back anyway so who cares. (the carrier said they will just swap it for me if they can see it not working)
So I let it finish and turn it on to see what happens, run through the setup to make sure it still crashes at the same spot so I can show them... and it doesn't crash... wtf?
So I flash the custom recovery and XNote... And it seems to be working now. Now freezing, no nothing... I... I don't know...

Crazy, least it appears somewhat sorted lol

radicalisto said:
Crazy, least it appears somewhat sorted lol
Click to expand...
Click to collapse
So far, yeah... I think I got the runt of the litter or something... Haha

Reynbow said:
So far, yeah... I think I got the runt of the litter or something... Haha
Click to expand...
Click to collapse
Just out of curiosity, as I see you have an AU model, did you buy it from Kogan? -- Reason I ask is that they used HK firmware on some models and HK models have issues flashing normal firmware (similar to the issue you had)

radicalisto said:
Just out of curiosity, as I see you have an AU model, did you buy it from Kogan? -- Reason I ask is that they used HK firmware on some models and HK models have issues flashing normal firmware (similar to the issue you had)
Click to expand...
Click to collapse
Not from Kogan, no. From Optus. Pretty standard.

What caused the soft brick?

Ok, I sold my S4 i9505 (rooted and stock firmware 5.0.1) on evilbay and it was working perfectly when I sent it. 10 days after it got to the buyer they say it won't boot and want to return the phone. I'm extremely suspicious and would like to know if it is possible to find out if they have installed something they shouldn't have. A phone doesn't suddenly soft brick itself or does it?

schnurrbidurr said:
Ok, I sold my S4 i9505 (rooted and stock firmware 5.0.1) on evilbay and it was working perfectly when I sent it. 10 days after it got to the buyer they say it won't boot and want to return the phone. I'm extremely suspicious and would like to know if it is possible to find out if they have installed something they shouldn't have. A phone doesn't suddenly soft brick itself or does it?
Click to expand...
Click to collapse
What does he mean with wont boot. The phone doesnt even turn on or he gets bootloop at samsung logo etc..?

obol2 said:
What does he mean with wont boot. The phone doesnt even turn on or he gets bootloop at samsung logo etc..?
Click to expand...
Click to collapse
I assume bootloop, because she said it was "constantly stuck in re-boot" . She apparently managed to get into Recovery Mode. I haven't got the phone back yet, but wanted to make sure I got all the info beforehand.

schnurrbidurr said:
I assume bootloop, because she said it was "constantly stuck in re-boot" . She apparently managed to get into Recovery Mode. I haven't got the phone back yet, but wanted to make sure I got all the info beforehand.
Click to expand...
Click to collapse
Have you done a full wipe before you give it away? Maybe wiped the system partition?

aboodyaiman said:
Have you done a full wipe before you give it away? Maybe wiped the system partition?
Click to expand...
Click to collapse
I did a full factory reset and did a quick test boot afterwards - all was ok. I may have wiped the cache partition but I'm pretty certain that that I didn't delete the system partition.

Does it has guarantee? When yes how long it left.
If you get the phone back I would flash a stock rom from sammobile with Odin, reboot and if it comes to the setup wizard you can give it her back .

obol2 said:
Does it has guarantee? When yes how long it left.
If you get the phone back I would flash a stock rom from sammobile with Odin, reboot and if it comes to the setup wizard you can give it her back .
Click to expand...
Click to collapse
Ultimately that's what I'll do, but I won't be sending it back to her. I'm already £££s out of pocket.
Honestly, I think she played about with it and messed it up. It took her 10 days to contact me. And since I booted the phone to the setup screen before I shipped it and it was working fine.
But I would like to know if it's possible to find out if and what she did and subsequently prove that