So it has been quite some time since I've been on these forums or tinkered with any phones. I believe the last one I rooted was a Thunderbolt.
Anyways, I have recently tried to root my Note 4 Edge and I hate to say it but I got cocky and rushed through it and now I am in trouble. (I know -- stupid)
I followed this guide (http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993) and everything was working right, followed the steps and what not. Unfortunately I did not create a backup of my last known working boot (Again, stupid, I know.) Needless to say, when I went to boot my phone up it was in a boot-loop. So I tried a wipe of everything using TWRP, everything except Micro SD and internal storage. Tried it again after the wipe, I get an message from TWRP saying that I have no OS (oh, great to see after flashing a rom).
After messing with that for an hour or two just to try and get my phone "working" again I gave up on it and tried using a ROM called HyperDrive, I think it's called. Wiped everything needed before flashing the rom, installation went smoothly, no "NO OS" message from TWRP. Rebooted phone, and what do you know, another boot loop.
Its been a while since I've tried tinkering with my phone, if anyone knows of what I did wrong or knows how to fix it I would greatly appreciate it considering ill need my phone for work tomorrow.
Please, and thank you.
Of course you wiped the system so no OS, i suggest you flash the stock rom via Odin first.
Related
So i decied to go to carbon rom because my phone has been acting strange, YouTube would keep resigning in everything i would launch it, Random crashed and freezes and has just been acting up for no good reason. I was running CM 10.1 nightly and dont apply ant mods to it or anything like that becuase i like it simple.
When i flashed the rom i did it with gapps but they were not intalled when i boot, all i got was my SIM pin popup like i usualy get. So i re-flashed gapps and still no luck. So i said f*** it and found another build of it and copyed it to my SD Card and was going to flash it. Like i allways do i went to factory reset and all i got was a long log of cant remove lost+found and same happed when i tryed to wipe the system. and that didnt look good so i pulled the battery and booted recovery with the key press and it would get to teamwin screen but would reboot. Opened oden on my desktop, reflashed teamwin tar and that didnt help it. So i was lucky that i loaded the rom and i rebooted to recovery and am copying all my /data/media to a sdcard that i have
So can anyone give me some links to the 16GB PIT and all that jazz so i can get thing back up and running
And no i am not a n00b becasue i have been working with android and other phones long enough to know what i am doing
powercamg4 said:
So i decied to go to carbon rom because my phone has been acting strange, YouTube would keep resigning in everything i would launch it, Random crashed and freezes and has just been acting up for no good reason. I was running CM 10.1 nightly and dont apply ant mods to it or anything like that becuase i like it simple.
When i flashed the rom i did it with gapps but they were not intalled when i boot, all i got was my SIM pin popup like i usualy get. So i re-flashed gapps and still no luck. So i said f*** it and found another build of it and copyed it to my SD Card and was going to flash it. Like i allways do i went to factory reset and all i got was a long log of cant remove lost+found and same happed when i tryed to wipe the system. and that didnt look good so i pulled the battery and booted recovery with the key press and it would get to teamwin screen but would reboot. Opened oden on my desktop, reflashed teamwin tar and that didnt help it. So i was lucky that i loaded the rom and i rebooted to recovery and am copying all my /data/media to a sdcard that i have
So can anyone give me some links to the 16GB PIT and all that jazz so i can get thing back up and running
And no i am not a n00b becasue i have been working with android and other phones long enough to know what i am doing
Click to expand...
Click to collapse
I think this is what you are looking for. Follow the guide and you will be on stock, rooted, and unlocked.
http://forum.xda-developers.com/showthread.php?t=2046439
mapatton82 said:
I think this is what you are looking for. Follow the guide and you will be on stock, rooted, and unlocked.
http://forum.xda-developers.com/showthread.php?t=2046439
Click to expand...
Click to collapse
Iv been able to load a rom but now i cant write to the phone, i have now found a guide talking about unbricking it useing odin anf a nand erase all and thats not working eather, any story i can tell verizon so i can get a replacement today?
Update!
Iv been useing http://forum.xda-developers.com/showthread.php?t=1840030 to try to get my phone back and so far it has failed but i decied to switch computers, all my computers are now running windows 8 and i ws doing this on my development computer / server and then i switched to the last computer to have windows 7 next to my main computer and what do you know it worked, the nand erase worked and now its booting im sure i will have to re-unlock the bootloader and all but im happy now
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
ransdell2 said:
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
Click to expand...
Click to collapse
It's definitely hard bricked, whatever happened is very strange though, as a nandroid doesn't usually mess up your boot partition.
Flashing a rom not intended for your phone can cause a hard brick, but that's not the only way it can happen. Somewhere in the restore process your boot partition got corrupted. Your base coding somehow is not being recognized, and your computer and phone can't tell what's supposed to run. A jtag is really your only option.
TWRP offers you the option to disable the boot and recovery partition when restoring. After you fix your phone, I'd recommend trying that out so you're absolutely sure your boot partition doesn't get touched. Those really don't need to be restored anyway.
Sorry that happened to you.
Sent from my SCH-I535 using Tapatalk 2
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
ransdell2 said:
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
Click to expand...
Click to collapse
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
ransdell2 said:
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
Click to expand...
Click to collapse
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Great, thanks for the info! I'll make sure that the boot and recovery partitions aren't touched in the future. I've primarily used CWM, but am probably just going to stick with TWRP.
I've been trying to upgrade to a LiquidSmooth KitKat (3.0 Nightly Beta) ROM but it's been failing. So I figured it's Sunday, it's early, let me try again. Let's get a baseline:
Last usable (as of earlier this morning) ROM: LS 2.7 (4.2.2)
TWRP 2.6.3.0
SuperSU installed
So I *WAS* unlocked and rooted.... now... I don't know what the heck is wrong.
Saturday I downloaded "EZ Unlock 1.2" and installed it; Unlock Status was "UNKNOWN" and even after clicking the UNLOCK button it still showed "UNKNOWN"
So, this morning, I made sure I had the new ROM (LS KitKat 3.0 Nightly Beta 2) on my external SD card, booted in to TWRP, and updated to the latest TWRP (2.6.3.1). I then cleaned out some old ROM backups and made a new one (using compression) which was successful. Rebooted to system, all looked & worked normally, so I rebooted to TWRP Recovery, did a Factory Reset + system (so cache, dalvik, data, & system) and that went fine. Tried to install the new ROM... FAILED. So I rebooted to Recovery and tried to restore the backup I had just made, and it seemed to succeed, but when the phone rebooted, it only got to where it reads "Samsung Galaxy S III" and got no further. I let it sit like that for 10 minutes, then pulled the battery. I booted back in to Recovery and tried restoring a backup made 2 days ago (that I have previously restored from successfully) and that gave a "successful" result, but same thing after rebooting: stuck at where it reads "Samsung Galaxy S III" and would go no further.
I am in DOWNLOAD mode currently and want to get back to the point of being able to restore my backup from 2 days ago. I'll lose text messages basically, and that's fine. I have downloaded ODIN 3.07 but it's been about a year since I last tinkered with it.
Can someone help please? I either get this phone working in the next few hours, or I have to go buy something else off craigslist... or full retail... and I'd really just prefer to get this phone working again.
If I need to "start from ground zero" and redo the boot unlock and root it, so be it. Basically, how do I unbrick my S3?
papadelogan said:
I've been trying to upgrade to a LiquidSmooth KitKat (3.0 Nightly Beta) ROM but it's been failing. So I figured it's Sunday, it's early, let me try again. Let's get a baseline:
Last usable (as of earlier this morning) ROM: LS 2.7 (4.2.2)
TWRP 2.6.3.0
SuperSU installed
So I *WAS* unlocked and rooted.... now... I don't know what the heck is wrong.
Saturday I downloaded "EZ Unlock 1.2" and installed it; Unlock Status was "UNKNOWN" and even after clicking the UNLOCK button it still showed "UNKNOWN"
So, this morning, I made sure I had the new ROM (LS KitKat 3.0 Nightly Beta 2) on my external SD card, booted in to TWRP, and updated to the latest TWRP (2.6.3.1). I then cleaned out some old ROM backups and made a new one (using compression) which was successful. Rebooted to system, all looked & worked normally, so I rebooted to TWRP Recovery, did a Factory Reset + system (so cache, dalvik, data, & system) and that went fine. Tried to install the new ROM... FAILED. So I rebooted to Recovery and tried to restore the backup I had just made, and it seemed to succeed, but when the phone rebooted, it only got to where it reads "Samsung Galaxy S III" and got no further. I let it sit like that for 10 minutes, then pulled the battery. I booted back in to Recovery and tried restoring a backup made 2 days ago (that I have previously restored from successfully) and that gave a "successful" result, but same thing after rebooting: stuck at where it reads "Samsung Galaxy S III" and would go no further.
I am in DOWNLOAD mode currently and want to get back to the point of being able to restore my backup from 2 days ago. I'll lose text messages basically, and that's fine. I have downloaded ODIN 3.07 but it's been about a year since I last tinkered with it.
Can someone help please? I either get this phone working in the next few hours, or I have to go buy something else off craigslist... or full retail... and I'd really just prefer to get this phone working again.
If I need to "start from ground zero" and redo the boot unlock and root it, so be it. Basically, how do I unbrick my S3?
Click to expand...
Click to collapse
Have you try to wipe cache/dalvik cache/system/ format sd, make sure everything is mounted the do the restore again?
buhohitr said:
Have you try to wipe cache/dalvik cache/system/ format sd, make sure everything is mounted the do the restore again?
Click to expand...
Click to collapse
I am currently backing up my external SD card (all pics & backups go to ExtSDCard) before doing any formatting. I was going to try that next, but am expecting it to fail. What I've found on XDA so far has mostly for those that took an OTA but that is not my case. I am severely pressed for time (use my phone for work as well as personal) and am planning for "worst case scenario" so, assuming your suggestion fails, do I get the original ROM, flash that back using ODIN, then re-do the boot unlock & root?
papadelogan said:
I am currently backing up my external SD card (all pics & backups go to ExtSDCard) before doing any formatting. I was going to try that next, but am expecting it to fail. What I've found on XDA so far has mostly for those that took an OTA but that is not my case. I am severely pressed for time (use my phone for work as well as personal) and am planning for "worst case scenario" so, assuming your suggestion fails, do I get the original ROM, flash that back using ODIN, then re-do the boot unlock & root?
Click to expand...
Click to collapse
That would be the right way..good luck!
buhohitr said:
That would be the right way..good luck!
Click to expand...
Click to collapse
I was hoping for a bit more than "good luck" actually since it's been a good year since my last trip with Odin... but thanks.
papadelogan said:
I was hoping for a bit more than "good luck" actually since it's been a good year since my last trip with Odin... but thanks.
Click to expand...
Click to collapse
I have high confidence that you will have this issue resolved shortly. It's not your fault, lately, some custom roms did not behave accordingly...
Hey guys, I was gifted a transformer tf700t, well I tried doing custom ROM's or some **** or tried putting a new OS on it, and now it's all ****ed up. It tries to boot into "Cromi-K" or some ****, but I can go into recovery I think it's called and use TWRP or the other popular one and flash images, only I don't know what images to flash to just get it back to stock, and every image I try it fails to flash it.. even after I clear cache and clear everything else. All I want is it back to stock and running again. I'll pay like $10 BTC if that's allowed if someone can help me. I also dont know anything about using commands from the PC and pushing it to the tablet.. so..
If you can help, my Skype is: Goldstingz
Thanks
this happened when i rooted, installed freedom, left freedom on, and reformatted, then it ****ed up. so i tried crombi. and idk ive tried a lot.
I have a well and heavily used Galaxy S5 (GM-900P) and about 2 months ago it started accting up pretty hard. Becoming very very slow so I decided to update to the latest sprint firmware and install a new(er) rom ([ROM][QD1][6.0.1]14Dec2017] Stock-ish Plus Tidbits and Magisk) and all was good for about 5 days and the phone started having apps crash/force close like crazy and most the time just reinstalling them would fix it but a bunch of google play services would crash and would have to uninstall the updates then it would work again for a day or so, sometimes it would randomly restart and get stuck at the boot screen and the phone would get crazy hot and the only way out of it was to boot into the recovery and then reflash the stock firmware in odin again then reinstall the rom. Then I had my phone all of a sudden act like there was no sim card in it and originally though it was a sim card issue but turns out it wasnt, I had to boot into the recovery and do a full wipe of everything reflash the stock firmware yet again and then reinstall the rom again. That happened twice in a matter of a week. At my wits end I decided to give LineageOS v16 a try so I boot into recovery, do a full wipe, boot into download mode, flash the latest stock firmware in odin, then boot right to recovery, flash LineageOS 16.0 then latest Magisk and all was great, for about a week, then Google services start crashing again and random apps crash over and over and even times the phone would slow down and reboot, get stuck at the boot screen and then eventually just reboot back into recovery by itself after failing to boot. But with LineageOS at least just reflashing the rom in the recovery will let it boot right back up sometimes and work as it should for another few days, other times too much stuff will just keep crashing so I do a full wipe and reflash LineageOS and all will be great for another few days to a week and it starts all over again. Its like stuff just randomly gets corrupted on the device and the only way out of it is to reflash the whole thing and start over and enjoy it until it does it again. Sometimes it will go days, sometimes a day later its all screwy again.
Also, TWRP always fails when I try to do a back up and it seems to always fail when in the data or data/private-app part of the system and its never at the same point.
I guess my question here is, could the onboard flash (the motherboard/logic board) be taking a crap on me? I really really dont want to give up on this phone just yet as it has everything I want in a phone and frankly, I just really really like it. I can get a new (used) motherboard for like $20 but even that kind of worries me cause I dont want to possibly be in this same position 3 months later again. I have a Galaxy S8+ (unlocked AT&T phone) that I refuse to use yet just cause I can not root it or unlock the bootloader.
Any help or ideas would be much appreciated and sorry for the long winded post.
could be wrong, on this one, But.....
If it was mew, I would go to stock . run that for a day, maybe 3... if all it well, then flash over what ever Rom you would like.
"KNOWING IT Work" is the key. Oh, another thing, that may help too . seen this on one of the LineageOS 15.1 or 16 is when you wipe ... System and Data, can be Reformatted, they have had some major success by also formatting it, (YES EXT4) but this will help to ensure nothing left over....
May even help with others Android 8.0, 8.1, 9.0....
Well, I have a new motherboard on the way so we'll see how that goes but I did manage to get the stock firmware on there and booted then I reflashed TWRP and then Magisk and going to just run it that way for a bit and see what happens.
I initially went in to TWRP, wiped data,system, etc... then flashed the stock firmware in Odin, then rebooted, got stuck at the Samsung boot logo so pulled the battery, booted to stock recovery, did a factory reset (Wiped everything, internal sd card included), then got it to boot, set the phone up, then rebooted to download mode, flashed TWRP, then rebooted again, set the phone up a bit more then decided to flash Magisk so I have root, and so far its working. 100% stock with magisk. Fingers crossed.
I still think there is an issue with the internal flash memory though as I can not get a TWRP backup to actually complete without failing. It always fails when backing up stuff in the data partition/section and never at the same point like its having read errors or something. I'll grab a TWRP log and post it up in a bit.
Well, that didnt last long. Within an hour, apps started crashing. I will make this thing work! LoL